FAQ
A few questions and answers for those who might wonder why, what, who and how.
-
1. What's the shortest schedule I can create?
One minute is currently the minimum allowed schedule length.
-
2. What is a typical use/real world example for http.sh?
Lets say I have an online shop and on Mondays I want it to fetch the latest news from the manufacturers RSS feeds and cache/save that information. I write a PHP/.NET/other script on my website to do the fetching and the caching of the RSS and I now just need a way to get it to do so every Monday.
I might also add a secret key (so exploring search engines/users accidentally hitting the URL don't execute it) or need to pass some variables to the script to tell it what to-do.
That's where I can login to my http.sh account and add a new schedule:
Name: MyShop RSS
URL: http://myshop.sh/getRss.php
Request method: GET
Variables to pass: secretKey=eb252bace2ab6282bae6c708cc65019f&action=cache
Frequency: Mondays only -
3. Is there a limit to the number of schedules?
Schedules are currently limited to 20 per account to prevent abuse.
-
4. Is there a limit to the number of accounts?
Multiple accounts are not permitted in most circumstances. I will actively squish anyone abusing/using multiple
accounts to circumvent the 20 schedule limit without contacting us first. -
5. I like the design, where is it from?
The original design was provided from http://templates.arcsin.se/ via http://oswd.org/.
-
6. How long will my schedules continue to run?
Many people now rely on http.sh running smoothly for day-to-day business, incl. the developers and maintainers of the project.
That being said, this service is provided free of charge and there are no warranties, guarantees or official policies.
I don't plan on going anywhere... -
7. How does http.sh make money?
It is not always about the money, plus my hosting costs are minimal.
-
8. I found a bug or have a feature request, where can I send it?
Please contact smtp@http.sh for all bugs, features and questions.
-
9. Is http.sh open source?
If enough people are interested in the code behind http.sh to justify full documentation and creation as
an open source project we'll happily do so.
