Hi Chris,

If you are not actively developing the code anyways, can you please just publish an archive of the source code (with history imported from SVN if possible) to GitHub?

I am not saying you need to use GitHub as a collaborative tool, but just publish it so it is public for people to look at an inspect. Also git repositories are very portable, so you can just move it to gitlab when you have one properly set up, and even still have a mirror on github if you want.

Or just put it on a GitLab server, I just feel like there is a risk for it to never get done otherwise.

And if even that is too much work, just send a zip file here with it all and someone else can put it on github if you are not developing it further. I would prefer the other options but just having it private for no reason is worse.

-Cynthia

On Sat, Apr 3, 2021 at 2:51 PM G1FEF via 44Net 44net@mailman.ampr.org wrote:

...

Chris: simple question; *where* is the code?

The Portal server contains all the code (obviously) and it is backed up once every 24 hours by taking a snapshot of the VM, so if the hardware fails it can be recreated on another server in the same DC. The database the Portal uses is a different VM on separate hardware which is also backed up daily. All the snapshots are replicated offsite in case of a site wide disaster.

I also have a copy of the code and database schema on my main desktop and my laptop, these are clones of an SVN repo which is on a server in a different datacenter to the above VMs. Although I am not actively developing the code anymore, I still use the SVN repo in case anyone finds a bug which I can then fix and deploy to the live server.

Regards, Chris - G1FEF

---

44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net