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

Figure out existing infrastructure/hosting #51

Open
2 tasks
tyliec opened this issue Nov 25, 2023 · 0 comments
Open
2 tasks

Figure out existing infrastructure/hosting #51

tyliec opened this issue Nov 25, 2023 · 0 comments
Labels

Comments

@tyliec
Copy link
Member

tyliec commented Nov 25, 2023

Objective

The primary objective of this task is to conduct a thorough assessment of the existing infrastructure and hosting setup for UIPA.org. This includes identifying the current hosting provider, server configurations, and any associated services, with the aim of gaining a comprehensive understanding of the project's hosting environment.

Additional Information

A previous email sent to the administrator of the UIPA.org system
Hello, Todd.

I hope this email finds you well. I'm Tyler Chong from the Code with Aloha team, and I have some technical questions regarding access to the server that houses the UIPA.org system. Brian mentioned that you could provide assistance with these inquiries, and I appreciate your willingness to help.

Specifically, I'd like to know:

1. What type of server is UIPA operating off of (where is it hosted, who has access, ...etc)

It's a linux virtual machine in a data center I operate. I am basically the only one with direct access to it.

2. Is it possible for us to get access to the server? Or what would a deployment workflow look like (Do we pass someone a USB stick? 😆)

Anything is possible, but I think (or at least thought) the idea was to spin up a new server/platform vs. updating the current one due to it's very aged base-OS and packages. Is that not the case?

3. What would a workflow look like for us to do maintenance? Would we contact someone to make the change for us? Or would we redeploy the app entirely.

Right now I could help facilitate changes, but depending on what the plan is for up-revving it might make sense to  come up with a different process.

Success Criteria

  • Document what the infrastructure Looks Like
  • Document how to access said infrastructure

Related Items

Parent Epic: #42

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

No branches or pull requests

1 participant