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

Try to create a Docker image for the web server. #10

Open
bdklahn opened this issue Jan 26, 2022 · 8 comments
Open

Try to create a Docker image for the web server. #10

bdklahn opened this issue Jan 26, 2022 · 8 comments
Assignees

Comments

@bdklahn
Copy link
Member

bdklahn commented Jan 26, 2022

Perhaps we could use do something like this with Docker Compose:
Django and PostgreSQL

@hasanbaig
Copy link
Member

The link is not working.

@bdklahn
Copy link
Member Author

bdklahn commented Jan 26, 2022

Try now. Somehow an extra character made it's way into the link address.
Also, I just created this issue to document this, and possibilities.
At least most of the requirements could be packaged in a Docker image.

@bdklahn
Copy link
Member Author

bdklahn commented Feb 5, 2022

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).
https://pypi.org/project/django-webserver

@hasanbaig
Copy link
Member

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

@shoops
Copy link
Member

shoops commented Feb 16, 2022

Hasan it is easy for Brian to do that. He just needs access to the code.

@hasanbaig
Copy link
Member

Oh I see!
we will be merging the code to this repo soon. There are still some bugs that I am trying to fix. Once they are done, I will merge into this repo.

@bdklahn
Copy link
Member Author

bdklahn commented Feb 16, 2022

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.
I guess we don't know the situation in your repo. But we can help with any of these:

  • you have commits on your local master (as children of the master here)
  • . . . and maybe changes in your working directory you have not yet merged/committed
  • . . . or you have local development branch . . .
  • . . . or . . . ?

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.
Just let me know how I might help.
Thanks!

@hasanbaig
Copy link
Member

Thanks @bdklahn. Yes, I can create a separate branch and push my entire repo (privately maintained) over here. I will talk to @pmendes about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants