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

Research hosting provider components for app #31

Closed
digable1 opened this issue Jan 15, 2025 · 8 comments
Closed

Research hosting provider components for app #31

digable1 opened this issue Jan 15, 2025 · 8 comments
Assignees
Labels
backlog This indicates an item to be selected for addresssing user_story
Milestone

Comments

@digable1
Copy link
Contributor

digable1 commented Jan 15, 2025

User Story Description
As a development team,
I want to ensure we can host all components of our app such as the client, database (example: supabase - although supabase has hosting capabilities)
So that users can access the integrated app and use it via a browser and URL

Possibilities:

  • Github Pages
  • Netlify
  • Surge
  • Render
@chef-louis
Copy link
Contributor

While we don't have a complicated application, given the dynamic needs to making API calls to our persistence layer along with facilitating authorization, we are better off with using a more capable hosting service such as Netlify or Render. Both Netlify and Render have a free-tier.

I have some working experience with Netlify and it should service our needs although the free tier doesn't allow for managing multiple users on the same team (although this also seems to be case for Render). In terms of next steps, my goal is to get the hosting off the ground using Netlify as a starting point.

@digable1 digable1 added the backlog This indicates an item to be selected for addresssing label Jan 22, 2025
@digable1
Copy link
Contributor Author

Based on what you wrote, this could impact us: Don't we need multiple users in order to assign different roles and therefore access to each user?

I see several backlog tasks for this work:

We'll need implementation tasks once we have selected which ones we're going to use (unless it makes sense to add them now on backlog).

I do have a couple questions based on what you've written so far:

  1. Since you've mentioned multiple users are not allowed on the free tier, am I correct in assuming that will affect our ability to assign roles to those users?
  2. What will it take to handle multiple users and roles as specified in the requirements?

@chef-louis
Copy link
Contributor

chef-louis commented Jan 22, 2025

@digable1 My fault, I explained the users part poorly. That last paragraph* isn't in reference to the authentication story for our menu web application. The users I was talking about are the developers on our team that would potentially want to have access on the hosting provider's dashboard to be able to make admin changes on our host.

So in other words we can host our app on Netlify and Render but you and I won't be able to collaborate on their platform application like we are doing on Github right now.

My last point here will be to emphasize that either Netlify or Render should work for our hosting needs using their free-tier. I'll push forward with Netlify given my experience doing this before using that platform -- as far as our hosting needs are concerned I believe either would work just fine.

@digable1
Copy link
Contributor Author

Oh - sorry!

Can we make a "shared user" and provide the credentials to all of us (not in public over here, but maybe during our meeting)? I know, it's clunky and is a potential security hole, but will it get us through this voyage?

@chef-louis
Copy link
Contributor

Oh - sorry!

Can we make a "shared user" and provide the credentials to all of us (not in public over here, but maybe during our meeting)? I know, it's clunky and is a potential security hole, but will it get us through this voyage?

Great idea! This can actually apply to Supabase as well in which case I'll get those accounts setup and share the details with the group.

@chef-louis
Copy link
Contributor

I've setup a deployment of our main branch to Netlify (https://v53-tier3-team-38.netlify.app/).

Fairly simple right now but we can add more complexity as we go if we want (ie. CI/CD)

@digable1
Copy link
Contributor Author

YES!

Due to the time-frame, I want to see what you guys want to do about the pipeline, as opposed to publishing the instructions on how to do it manually. In other words, how complicated is this process, possibly hindering how you would document this.

@chef-louis
Copy link
Contributor

chef-louis commented Jan 22, 2025

Yah good question. Candidly I'm not a CI/CD expert but no better time to learn, right? I'll add myself a task to look into this and start documenting over there.

Separate point that you reminded me of, I created a separate Netlify account so if others want to use this 'shared' account let me know and I'll get the credentials over to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog This indicates an item to be selected for addresssing user_story
Projects
None yet
Development

No branches or pull requests

2 participants