MagicCrayon9342 wrote:

-unrelated- wrote:

ninjaMAR wrote:

(#18)

alwayspaytaxes wrote:

(#11)
Fly.io has decent specs on their free tier

I concur. I didn't put a credit card in, and my one free project still works

whadayamean

It does not let you launch an app without a card.

TheCommCraft wrote:

MagicCrayon9342 wrote:

-unrelated- wrote:

ninjaMAR wrote:

(#18)

alwayspaytaxes wrote:

(#11)
Fly.io has decent specs on their free tier

I concur. I didn't put a credit card in, and my one free project still works

whadayamean

It does not let you launch an app without a card.

Is that directed at @-unrelated-?

MagicCrayon9342 wrote:

TheCommCraft wrote:

MagicCrayon9342 wrote:

-unrelated- wrote:

ninjaMAR wrote:

(#18)

alwayspaytaxes wrote:

(#11)
Fly.io has decent specs on their free tier

I concur. I didn't put a credit card in, and my one free project still works

whadayamean

It does not let you launch an app without a card.

Is that directed at @-unrelated-?

yes

-unrelated- wrote:

MagicCrayon9342 wrote:

TheCommCraft wrote:

MagicCrayon9342 wrote:

-unrelated- wrote:

ninjaMAR wrote:

(#18)

alwayspaytaxes wrote:

(#11)
Fly.io has decent specs on their free tier

I concur. I didn't put a credit card in, and my one free project still works

whadayamean

It does not let you launch an app without a card.

Is that directed at @-unrelated-?

yes

But I asked them what they meant because the link said what they said

MagicCrayon9342 wrote:

(#20)

-unrelated- wrote:

ninjaMAR wrote:

(#18)

alwayspaytaxes wrote:

(#11)
Fly.io has decent specs on their free tier

I concur. I didn't put a credit card in, and my one free project still works

whadayamean

It does not let you launch an app without a card.

ninjaMAR wrote:

(#25)

MagicCrayon9342 wrote:

(#20)
-snip-

It used to. I think they recently changed their plans

• Possible but against TOS
  
• Impossible for most projects
  
• Credit card required
  
• No guide to set up
  

-unrelated- wrote:

Reply here for help setting up a server on one of these services or if you know any other than the ones listed here:

• github actions (iafu) (guide: here)
  
• pythonanywhere (rdfue)
  
• fly.io (mafku)
  
• deta.space (ifu?)
  
• more?
  

i = unlimited free runtime/bandwidth
r = almost unlimited free runtime/bandwidth (e.g. refresh needed every now and then or high limits)
m = limited free runtime/bandwidth (e.g. 1000 minutes per month)
a = arbitrary internet access (no limitation like on pythonanywhere)
d = database included
c = cheap but not free
f = free
k = credit card required
l = limited access
u = not ip banned
e = easy to set up
? = what???

Waakul wrote:

(#29)

-unrelated- wrote:

Reply here for help setting up a server on one of these services or if you know any other than the ones listed here:

• github actions (iafu) (guide: here)
  
• pythonanywhere (rdfue)
  
• fly.io (mafku)
  
• deta.space (ifu?)
  
• more?
  

i = unlimited free runtime/bandwidth
r = almost unlimited free runtime/bandwidth (e.g. refresh needed every now and then or high limits)
m = limited free runtime/bandwidth (e.g. 1000 minutes per month)
a = arbitrary internet access (no limitation like on pythonanywhere)
d = database included
c = cheap but not free
f = free
k = credit card required
l = limited access
u = not ip banned
e = easy to set up
? = what???

github workflows have limited run time per month and it'll stop automatically once that finished, you have to pay for unlimited.

-unrelated- wrote:

So we have:

• Possible but against TOS
  
• Impossible for most projects
  
• Credit card required
  
• No guide to set up
  

I think we need a guide for deta.space or a new option

1. Create an account using this link
   
2. Go to this url
   
3. Click “start building” and do step 1
   
4. Prepare for step 2: Put all your source files in <project folder>/src/. Pip/npm/cargo config files (such as requirements.txt) go outside of src/. I haven't experimented much but probably put everything that isn't one of these files (or the spacefile) should go in src/. If you use a venv or similar, put that folder somewhere completely unrelated. If deta.space sees it nothing will work.
   
5. Do step 2.
   
6. If the spacefile is empty or only has 2 lines, go through this page and add the relevant stuff
   
7. At this point you should have:
   

   ~/
   |- venv (if you have it)
   |- project folder
     |- Spacefile
     |- Package manager files (eg. requirements.txt)
     |- src/
       |- <everything else>

8. Do step 3. If it complains about the spacefile being wrong, do #5
   

davidtheplatform wrote:

(#32)

-unrelated- wrote:

So we have:

• Possible but against TOS
  
• Impossible for most projects
  
• Credit card required
  
• No guide to set up
  

I think we need a guide for deta.space or a new option

Deta.space guide:

1. Create an account using this link
   
2. Go to this url
   
3. Click “start building” and do step 1
   
4. Prepare for step 2: Put all your source files in <project folder>/src/. Pip/npm/cargo config files (such as requirements.txt) go outside of src/. I haven't experimented much but probably put everything that isn't one of these files (or the spacefile) should go in src/. If you use a venv or similar, put that folder somewhere completely unrelated. If deta.space sees it nothing will work.
   
5. Do step 2.
   
6. If the spacefile is empty or only has 2 lines, go through this page and add the relevant stuff
   
7. At this point you should have:
   

   ~/
   |- venv (if you have it)
   |- project folder
     |- Spacefile
     |- Package manager files (eg. requirements.txt)
     |- src/
       |- <everything else>

8. Do step 3. If it complains about the spacefile being wrong, do #5
   

You now have a test URL which only works if you're signed in. If you want other people to see it, go to deta.space/builder, click on the app, go to publish, create release, then fill out the information. Make sure the publicly avaliable toggle is off. (this will only make it non-searchable, people with the link can still access it).

I just realized deta.space probably won't work for long-running things, it's intended for everyone to have a different instance of an app. So not as useful as normal hosting ¯\_(ツ)_/¯

-unrelated- wrote:

davidtheplatform wrote:

(#32)

-unrelated- wrote:

So we have:

• Possible but against TOS
  
• Impossible for most projects
  
• Credit card required
  
• No guide to set up
  

I think we need a guide for deta.space or a new option

Deta.space guide:

1. Create an account using this link
   
2. Go to this url
   
3. Click “start building” and do step 1
   
4. Prepare for step 2: Put all your source files in <project folder>/src/. Pip/npm/cargo config files (such as requirements.txt) go outside of src/. I haven't experimented much but probably put everything that isn't one of these files (or the spacefile) should go in src/. If you use a venv or similar, put that folder somewhere completely unrelated. If deta.space sees it nothing will work.
   
5. Do step 2.
   
6. If the spacefile is empty or only has 2 lines, go through this page and add the relevant stuff
   
7. At this point you should have:
   

   ~/
   |- venv (if you have it)
   |- project folder
     |- Spacefile
     |- Package manager files (eg. requirements.txt)
     |- src/
       |- <everything else>

8. Do step 3. If it complains about the spacefile being wrong, do #5
   

You now have a test URL which only works if you're signed in. If you want other people to see it, go to deta.space/builder, click on the app, go to publish, create release, then fill out the information. Make sure the publicly avaliable toggle is off. (this will only make it non-searchable, people with the link can still access it).

I just realized deta.space probably won't work for long-running things, it's intended for everyone to have a different instance of an app. So not as useful as normal hosting ¯\_(ツ)_/¯

No dev mode…

davidtheplatform wrote:

-unrelated- wrote:

davidtheplatform wrote:

(#32)

-unrelated- wrote:

So we have:

• Possible but against TOS
  
• Impossible for most projects
  
• Credit card required
  
• No guide to set up
  

I think we need a guide for deta.space or a new option

Deta.space guide:

1. Create an account using this link
   
2. Go to this url
   
3. Click “start building” and do step 1
   
4. Prepare for step 2: Put all your source files in <project folder>/src/. Pip/npm/cargo config files (such as requirements.txt) go outside of src/. I haven't experimented much but probably put everything that isn't one of these files (or the spacefile) should go in src/. If you use a venv or similar, put that folder somewhere completely unrelated. If deta.space sees it nothing will work.
   
5. Do step 2.
   
6. If the spacefile is empty or only has 2 lines, go through this page and add the relevant stuff
   
7. At this point you should have:
   

   ~/
   |- venv (if you have it)
   |- project folder
     |- Spacefile
     |- Package manager files (eg. requirements.txt)
     |- src/
       |- <everything else>

8. Do step 3. If it complains about the spacefile being wrong, do #5
   

You now have a test URL which only works if you're signed in. If you want other people to see it, go to deta.space/builder, click on the app, go to publish, create release, then fill out the information. Make sure the publicly avaliable toggle is off. (this will only make it non-searchable, people with the link can still access it).

I just realized deta.space probably won't work for long-running things, it's intended for everyone to have a different instance of an app. So not as useful as normal hosting ¯\_(ツ)_/¯

No dev mode…

You have to turn it on when you create an account apparently

dynamicsofscratch wrote:

i love the fact that it says in a “like pythonanywhere” but in the pythonanywhere lettering “a” is not anywhere (get it like anywhere and pythonanywhere)

-cloudcoding- wrote:

(#39)
Do you think anyone would really care about GitHub actions?