Major Feature #48407

New server for tools.typo3.org

Added by Ernesto Baschny over 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Target version:
-
Start date:
2013-05-21
Due date:
% Done:

0%


Description

To start working on the topic, a new virtual machine for "tools.typo3.org" is required. This has to be created by the Server Team.

Fabien Udriot suggested "bootstrapping a server on ms07 as instance. Will be srv145 if none one has been created recently." so I guess he also has the authority to do so?

Input or acknowledgement from Steffen Gebert would be great.

We want the machine to host several "little tools", so that we need a way of granting access to specific persons working on specific tools.

I offered my help in administring this machine. And am also open for infrastructural suggestions (i.e. management through chef), but that would require some "kick start" by some typo3-Chef-expert.

Otherwise some SSH access would help for a "faster start". :)

History

#1 Updated by Ernesto Baschny over 6 years ago

I just down-voted this issue by mistake. There doesn't seem a way of "unvote" it. :)

Xavier Perseguers also seem to be interested in the tools.typo3.org for his new "json" output experiment of TER.

#2 Updated by Steffen Gebert over 6 years ago

Hi Ernesto,

we've created a repo: https://git.typo3.org/Sites/ToolsTypo3Org.git

Please push your code into that repo. I will set up a chef cookbook here, which deploys the code every 30min ASAP.

When cron jobs are required, we can add them easily to that cookbook.

Steffen

#3 Updated by Ernesto Baschny over 6 years ago

Steffen, thanks a lot for your help and the machine.

What do you mean with "your code"? I currently only see an "index.html" in that repository. Does that mean I should push the static HTML files there?

What about the PHP script itself or the checked out repositories - which are not meant to be placed in the "htdocs" folder: should I keep this running on my machine and make it "push" it every hour to this repo instead? Does it make sense to have a commit each hour and keep a history of the whole "merged to core" html files? I thought the script was going to be running at the machine itself.

#4 Updated by Fabien Udriot over 6 years ago

What do you mean with "your code"? I currently only see an "index.html" in that repository. Does that mean I should push the static HTML files there?

Not only static HTML files but also PHP code which will be deployed automatically every 30 min by Chef. I guess it is just temporary, you will also get direct access on the server and update the repository to your convenience (at least it is how I imagine that). Since tools.typo3.org is a composite of tools, it could also have submodule per tool, just a thought.

#5 Updated by Steffen Gebert over 6 years ago

But stupid me forgot to set up PHP :-(

#6 Updated by Ernesto Baschny over 6 years ago

That's nice, but as I said already:

The "merged-to-core" is not a PHP script to be run through a Webserver. It's (currently) just a "PHP CLI script" which generates a bunch of static HTML files which need to be placed in a "public place". The PHP CLI script needs to work on local working copies of the TYPO3 core repositories and this all should not be accessible through the Web.

Since the generation is done every two hours, I find it pretty inconvenient to "push" a "change" every two hours just to update the state of the page.

Could you clarify how we can proceed? Maybe I could get some access to the machine temporarily so that I could setup how I think it "should work" and then you take a look at it and transform that into relevant chef receipts and git repositories?

Thanks!

#7 Updated by Fabien Udriot about 6 years ago

I have sent an email to Xavier and Ernesto with some info. Without more feedback the ticket can be closed.

#8 Updated by Steffen Gebert over 2 years ago

  • Status changed from Accepted to Resolved

#9 Updated by Steffen Gebert over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF