Frequently Asked Questions

Do I need to know how to program?

No. Recommended Templates and the portal workflow are designed for first-time users. You may still work with Codex or a developer to customize behavior beyond the starter.

What is GitHub, and why does the portal use it?

GitHub is a managed online place for app code and change history. It gives Codex, reviewers, collaborators, and Azure publishing one supported source for the app.

What is Azure?

Azure is Microsoft's cloud platform. The portal uses Azure App Service to run each published web app. Apps may also receive an app-specific database and secure secret storage when required.

Which template should I choose?

Choose the Recommended Template whose examples most closely resemble your project. Use a Developer Starter only when a developer has identified the needed runtime or service type.

Can I change templates later?

Not as a simple switch. A template shapes the starter code and available features. Ask Codex or a developer whether adapting the current app or creating a new one is safer.

Does publishing make my app public?

No. Publishing makes the app run in Azure. At creation, choose either Cedarville sign-in required or Openly public on the internet. An openly public app can be used by anyone who knows or discovers its address. Cedarville sign-in limits entry to people who can sign in with their Cedarville account.

Is Share in Portal the same as making my app public?

No. Share in Portal lets signed-in Cedarville portal users see the app's name, description, and link. It does not change who can open the published app.

Does creating a starter publish it?

No. Launch App makes the starter and its managed repository, then stops. Publish the starter now starts Azure publishing immediately and is the only publish confirmation for an unchanged starter. Customize it with Codex first leads through GitHub access and setup before a later Publish to Azure action.

Do I need a GitHub account?

Not to publish an unchanged generated starter. You need one when Codex or a person must access the private repository. If you do not have one, the wizard opens GitHub signup and explains how to choose a username. After signup, enter that username - not your email address or display name. It appears after github.com/ in your profile address. The portal then sends and confirms the repository invitation.

What do I need before using Codex?

Install Git from Company Portal on Windows or CedarNet 2.0 on macOS, then completely quit and reopen Codex. For a generated app, make a new empty folder. For an app already on your computer, use its existing folder. In Codex, create a local Codex project from that folder and make it primary. Start the task inside the project; do not use Quick chat or a standalone task. The portal prompt handles Git commands and uses secure browser sign-in for GitHub. Never provide a password, personal access token, or SSH key.

What should I do when Codex asks for permission?

Read the request and allow only what the current app task needs. It is normal to allow the selected app folder, normal development commands, and secure browser sign-in that you complete yourself. Choose Allow once when it is available, unless Cedarville IT has approved a broader established workflow. Do not approve unrelated folders or applications, and never provide passwords, tokens, private keys, or portal credentials.

What is the difference between Continue Setup and Manage App?

Continue Setup returns an unpublished app to its focused first-publish wizard. Manage App appears after a successful first publish and opens the full app details page.

What happens after someone changes the code?

The change must be committed and pushed to the portal-managed GitHub repository. Then push-to-deploy may publish automatically, or an authorized portal user can select Publish to Azure.

Can another person help manage my app?

Yes. The owner or an administrator can invite a Cedarville coworker as a collaborator. The collaborator accepts through Cedarville sign-in and requests separate GitHub access when needed.

What does Repair Publishing Setup do?

It refreshes portal-managed GitHub and Azure publishing credentials and settings. It does not delete resources, change your app's code, or start a deployment.

Where should passwords and API keys go?

Use the app's Environment Variables area when instructed. Do not place real values in code, GitHub files, documentation, screenshots, chat messages, or email.

Can I delete the portal record but keep the live app?

Yes, because deletion scopes are separate. However, if you remove the portal record and keep GitHub or Azure, those resources will no longer appear in My Apps and may require manual IT assistance later.

Can deletion be undone?

Do not assume it can. Deleting a GitHub repository or Azure deployment may permanently remove code, history, configuration, or data. Coordinate and preserve anything required before deleting.

What should I include in a support request?

Include the app name, support reference, approximate time, action selected, and exact on-screen message. Never include passwords, secret values, private keys, or environment-variable contents.