-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Possible to create multiple projects from single repo? #1554
Comments
You can point RTD to the specific conf.py file for Sphinx in the Advanced We are hoping to add support for multiple translations within 1 project at On Tue, Aug 11, 2015 at 3:57 PM, Bruno Škvorc [email protected]
Eric Holscher |
That was the original idea, yes, but as I can only set up one project from a single repo, I don't get the change to set up several projects, each pointing to its own |
@Swader I think you can create a new project that uses the same repository url. You will have two distinct projects on RTD with different names that use the same repository. |
Ah, correct. So that worked and I have everything running smoothly on my local machine. My builds on RTD are failing, though - any help would be much appreciated. It keeps looking for the master file in the location of the custom Full build error here. |
Resolved via #1573 and in this project |
I have some Gettext translations all in a single repo, under /docs in my project. I can create a separate config file for every language, so that every language setup is essentially a translation of the original project, but is there a way to add multiple RTD projects via a single repository? I need this in order to not have to make a separate github repo for every one of the included languages - they have abstracted common parts and work fantastically in this single-repo setup, allowing all my users to update any language they see fit without leaving the repo. If I had to separate out all those languages into separate repos just to make new RTD projects and declare them as transactions, that'd be too much of a dealbreaker.
I saw some people did this, but I'm unclear on how they implemented it in RTD.
The text was updated successfully, but these errors were encountered: