-
Notifications
You must be signed in to change notification settings - Fork 1
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
Try to create a Docker image for the web server. #10
Comments
The link is not working. |
Try now. Somehow an extra character made it's way into the link address. |
I wonder if we could do/use something like this, rather than install Apache or nginx (nor use Django's built in dev web server). |
Sorry for late reply. I don't know why I did not receive a notification about it. I am not aware of this, but I will check it if we can use it for cloud-COPASI |
Hasan it is easy for Brian to do that. He just needs access to the code. |
Oh I see! |
Sounds good, @hasanbaig . And if you want any input on those bugs, it should be easy to push any changes from/on a separate branch, to here (GitHub) without any harm, before even having to try and merge anything back into master.
Whatever . . . If you've already made some commits to your master, and are apprehensive about destabilizing the master here, you can create a branch to save any committed (and need/want to commit work). Then you could check out your master and "reset" to match the one here. Then you can safely push your dev work branch here (unmerged into master). Anyway, it's not even that big of a deal if you want to push whatever you've got directly to master here. We'd just create and push a tag to annotate this "legacy stable" point in history, which anyone can easily go back to, if they want. |
Perhaps we could use do something like this with Docker Compose:
Django and PostgreSQL
The text was updated successfully, but these errors were encountered: