Changeset f67c75c in trunk
- Timestamp:
- 2024-08-22T17:08:51Z (8 months ago)
- Branches:
- master
- Children:
- 581349c
- Parents:
- 56c03a0e
- git-author:
- Florian Sesser <florian@…> (2024-08-09 18:35:18)
- git-committer:
- Florian Sesser <florian@…> (2024-08-22 17:08:51)
- Location:
- docs
- Files:
-
- 2 edited
- 3 moved
Legend:
- Unmodified
- Added
- Removed
-
TabularUnified docs/Installation/install-tahoe.rst ¶
r56c03a0e rf67c75c 40 40 tahoe --version 41 41 42 If you want to hack on Tahoe's source code, you can install Tahoe in a ``virtualenv`` on your Windows Machine. To learn more, see :doc:` install-on-windows`.42 If you want to hack on Tahoe's source code, you can install Tahoe in a ``virtualenv`` on your Windows Machine. To learn more, see :doc:`../build/build-on-windows`. 43 43 44 44 Linux, BSD, or MacOS … … 64 64 tahoe --version 65 65 66 If you are looking to hack on the source code or run pre-release code, we recommend you install Tahoe-LAFS on a `virtualenv` instance. To learn more, see :doc:` install-on-linux`.66 If you are looking to hack on the source code or run pre-release code, we recommend you install Tahoe-LAFS on a `virtualenv` instance. To learn more, see :doc:`../build/build-on-linux`. 67 67 68 68 You can always write to the `tahoe-dev mailing list <https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev>`_ or chat on the `Libera.chat IRC <irc://irc.libera.chat/%23tahoe-lafs>`_ if you are not able to get Tahoe-LAFS up and running on your deployment. -
TabularUnified docs/index.rst ¶
r56c03a0e rf67c75c 22 22 23 23 Installation/install-tahoe 24 Installation/install-on-windows25 Installation/install-on-linux26 Installation/install-on-desert-island27 24 28 25 running … … 71 68 contributing 72 69 CODE_OF_CONDUCT 70 build/build-on-windows 71 build/build-on-linux 72 build/build-on-desert-island 73 73 developer-guide 74 74 ticket-triage
Note: See TracChangeset
for help on using the changeset viewer.