Aggie Enterprise Deployment Steps
Open
Nobody has claimed this yet.
Aggie Enterprise
- Dominant language
- C#
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
- Edit the database to add the AE complete setting (Same place where KFS exists)
- Update the database
- Run the System page to get the latest values for Each, Dozen, etc.
- Look through all the config settings
- Do a dry run by getting a copy of the prod database again?
- Other things? Add as we think of them
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the database setting where KFS exists, the System page, and the configuration settings referenced in the checklist. Done means the Aggie Enterprise deployment steps are completed, including a confirmed database update and dry run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100