[tor-commits] [community/staging] Add terraform-onions and heroku. Fix #151

hiro at torproject.org hiro at torproject.org
Sun Mar 21 19:17:30 UTC 2021


commit c9bc488589746935764b2d6b0a457a62032e9514
Author: gus <gus at torproject.org>
Date:   Mon Dec 21 14:39:13 2020 -0500

    Add terraform-onions and heroku. Fix #151
---
 content/onion-services/setup/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/onion-services/setup/contents.lr b/content/onion-services/setup/contents.lr
index b872eaf..a95fe51 100644
--- a/content/onion-services/setup/contents.lr
+++ b/content/onion-services/setup/contents.lr
@@ -163,5 +163,5 @@ That is not an easy task, and these resources will help on how to make this poss
 
 Finally, if you plan to keep your service available for a long time, you might want to make a backup copy of the `private_key` file somewhere.
 
-Now that you have an onion site working, you may want to deploy [Onion-Location](https://community.torproject.org/onion-services/advanced/onion-location/), or use tools like Docker, [Ansible](https://galaxy.ansible.com/systemli/onion) or [stem](https://stem.torproject.org/tutorials/over_the_river.html) to automate the management of your onion services.
+Now that you have an onion site working, you may want to deploy [Onion-Location](https://community.torproject.org/onion-services/advanced/onion-location/), or use tools like Docker, [Heroku](https://gitlab.torproject.org/hiro/onions-on-heroku), [Terraform](https://gitlab.torproject.org/hiro/terraform-onions), [Ansible](https://galaxy.ansible.com/systemli/onion) or [stem](https://stem.torproject.org/tutorials/over_the_river.html) to automate the management of your onion services.
 If you have a static website, but never installed Nginx or Apache, another project to try is [OnionShare](https://onionshare.org), where running an onion site will be easier: guided with a graphic interface and with minimal configuration.





More information about the tor-commits mailing list