Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub deployment workflow #2887

Open
tmkarlsen opened this issue Dec 20, 2024 · 1 comment
Open

GitHub deployment workflow #2887

tmkarlsen opened this issue Dec 20, 2024 · 1 comment
Assignees

Comments

@tmkarlsen
Copy link
Member

The deployment to prod environments must be set up to give us better control

@tmkarlsen tmkarlsen converted this from a draft issue Dec 20, 2024
@Kamelon7
Copy link
Contributor

Currently, test and staging environments are automatically restarted to pull the latest Docker image each time a new one is built. This process isn't desirable for production environments.

Suggestion:
Create a manual process that tags a specific image with a tag (e.g. "stable" or "prod"). We can either add the server restart step here, or solve that part in AWS.

@tmkarlsen tmkarlsen moved this from 🆕 New to 📋 Backlog in Edlib 3 Jan 8, 2025
@tmkarlsen tmkarlsen moved this from 📋 Backlog to 🔖 Prioritized and ready in Edlib 3 Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔖 Prioritized and ready
Development

No branches or pull requests

3 participants