+++ This bug was initially created as a clone of Bug #5213 +++ > Both Marcom and Artwork require space on Mageia servers for storing artwork and > marketing texts. And Documentation team needs space too, as requested on 15/03/12 : http://www.mageia.org/pipermail/mageia-sysadm/2012-March/004270.html We need a ftp server to upload to and a subdomain like doc.mageia.org to be able to see our Calenco documentation as it is in this moment (it gets updated automatically when a change is made), but also to store finished versions that are meant for the public and that will be kept as history when a new finished version becomes available. The situation for documentation team is less urgent than for Marcom and Artwork, because we have server space outside Mageia, but I suppose it won't take much extra work to help us too, when helping them.
CC: (none) => doc-bugs
Depends on: (none) => 5915
Marja, the doc.mageia.org (see bug 5915) has been opened. Do you still need an FTP account or can you use the svn for that? (with a trunk for your current work in progress and branches for finished ones)
(In reply to comment #1) > Marja, the doc.mageia.org (see bug 5915) has been opened. Do you still need an > FTP account or can you use the svn for that? (with a trunk for your current > work in progress and branches for finished ones) @ Romain We can use SVN for finished work, but we need FTP for things we are working on. From within Calenco, something like http://doc.mageia.org/content/index.html can be automatically updated with every change, if it is on a ftp server. Seeing the changes you made almost immediately, helps a lot when writing or editing the documentation
(In reply to comment #2) > We can use SVN for finished work, but we need FTP for things we are working on. That sounds strange. > From within Calenco, something like http://doc.mageia.org/content/index.html > can be automatically updated with every change, if it is on a ftp server. Aren't you asking for a Web/HTTP server space instead? > Seeing the changes you made almost immediately, helps a lot when writing or > editing the documentation Why can't you see your changes locally as you edit the doc, or through Calenco itself?
(In reply to comment #3) > (In reply to comment #2) > > We can use SVN for finished work, but we need FTP for things we are working on. > > That sounds strange. > > > From within Calenco, something like http://doc.mageia.org/content/index.html > > can be automatically updated with every change, if it is on a ftp server. > > Aren't you asking for a Web/HTTP server space instead? Of course the idea is to see the documents with a common browser. From within Calenco we can only upload those documents (that get synchronised when changed) to an ftp server. I don't have a terrible problem with keeping the documents we work on on mageia.nl, though, if remmy doesn't object. > > > Seeing the changes you made almost immediately, helps a lot when writing or > > editing the documentation > > Why can't you see your changes locally as you edit the doc, or through Calenco > itself? We can, but it is much harder to see and some things you just don't see. We make and edit xml files, but we don't publish xml files. From the xml files html files are generated. Those are the ones where we can really see what we did :)
Ok, got it: Calenco => ftp location that gets published as http for review. So the request is: - a doc-test.mageia.org web site, - a ftp account to upload contents under the document root of it, - need of a cron or something, to generate the index.html page?
Summary: doc.mageia.org + ftp server for documentation team => doc.mageia.org + doc-test.mageia.org (with ftp upload)
Is there other protocols supported by Calenco, or is it only ftp ?
CC: (none) => boklm
(In reply to comment #5) > Ok, got it: Calenco => ftp location that gets published as http for review. > > So the request is: > - a doc-test.mageia.org web site, > - a ftp account to upload contents under the document root of it, > - need of a cron or something, to generate the index.html page? For the first two: yes For the third: probably yes (I miss some understanding, so I'm not sure, I'm only sure it would be nice if, from doc-test.mageia.org, we could click on links to the documents and/or the folders they are in, instead of having to type the full path) (In reply to comment #6) > Is there other protocols supported by Calenco, or is it only ftp ? Calenco was upgraded on may 26th, so I just looked to see whether anything changed in that regard, but ftp is still the only possibility.
Keywords: (none) => Atelier
you would probably should use the git for docs just create accounts in github.com create org and join it or setup git server - it is very useful and userfriendly thing sp after setting it up you will see all your changes in text - it's made for programmes and text there are kinda very-very-very needed.
CC: (none) => oeai
@ Ra Thx for your suggestions. For docteam, the first half of this bug has already been solved, though, it is only the 2nd half that still needs solving. So now adjusting the summary. We do have a good /temporary/ alternative for doc-test.mageia.org, thx to remmy, on docteam.mageia.nl. We'll keep using that as long as this bug isn't solved and that solution is available.
CC: (none) => remcoSummary: doc.mageia.org + doc-test.mageia.org (with ftp upload) => doc-test.mageia.org (with ftp upload)
CC: (none) => atelier-bugs
CC: mageia-artwork => (none)
CC: (none) => filip.komar
CC: boklm => (none)
We already have http://www-test.mageia.org/ but it's currently empty and no upload mechanism known to me ;). Maybe we can use that subdomain for such purpose?
Calenco supports sftp, too, now.
Summary: doc-test.mageia.org (with ftp upload) => doc-test.mageia.org with (s)ftp upload
CC: remco => (none)
Note that docteam no longer has an ftp server to upload the working versions of our documents to. Remmy has, since the very beginning, told us that his server was only temporarily available. We have used it half a decade, which is much longer than intended. mageia.nl (we used ftp to upload to docteam.mageia.org) is currently in quarantaine. https://www.sidn.nl/whois?q=mageia But a solution on mageia.org would be better :-)
If this is quicker for sysadmins to arrange, you can also add a DNS entry for docteam.mageia.org (or whatever), and point it to the following IP's: 178.62.201.32 2a03:b0c0:2:d0::58:1001 Just let me know when it's done and I'll amend things on my side.
For now, it is available at: http://178.62.201.32/~docteam/ I hope this will work for the moment.
(In reply to Remco Rijnders from comment #14) > For now, it is available at: http://178.62.201.32/~docteam/ > > I hope this will work for the moment. It doesn't, but ennael said in council meeting that Mageia can pay for mageia.nl and probably also pay for server space. Can you claim docteam.nl for the mageia.org organization (please contact ennael about that, I'll CC her in this report)
CC: (none) => ennael1
What about comment #13? It should take the sysadmin team just minutes (if that) to do this at no cost to anyone. Then, somewhere in the coming months or so, it can be set up on one of mageia's servers.
CC: (none) => remco
(In reply to Remco Rijnders from comment #16) > What about comment #13? It should take the sysadmin team just minutes (if > that) to do this at no cost to anyone. Yes, but that doesn't mean it can be done, soon. Their TODO lists are so long that they can't find the end, there are too many more things that urgently need to be done, too many of which will also only take minutes and apart from their jobs and families that need time, there's also the voluntary work several (if not all) of them do outside of Mageia..... they're _overloaded_. > Then, somewhere in the coming months > or so, it can be set up on one of mageia's servers. CC'ing Simonnzg, because we need a plan B if our sysadmins can't do all that. @ Simon, Could you help docteam with (sftp) server space and with maintaining it for the draft Calenco manuals that get created or updated? http://meetbot.mageia.org/mageia-meeting/2017/mageia-meeting.2017-10-03-19.05.html
CC: (none) => gm4nzg
Yes. I can host Plan B. Simon(nzg)
(In reply to Marja van Waes from comment #15) > (In reply to Remco Rijnders from comment #14) > > For now, it is available at: http://178.62.201.32/~docteam/ > > > > I hope this will work for the moment. > > It doesn't, Logging in with ftp works, and with ssh works, too... I downloaded everything in docteam/public_html and am currently uploading it to Simon's server > but ennael said in council meeting that Mageia can pay for > mageia.nl and probably also pay for server space. > > Can you claim docteam.nl Oops, that should be mageia.nl, of course! > for the mageia.org organization (please contact > ennael about that, I'll CC her in this report)
Our draft documents can be found here, now http://mageia.org.uk/ Unfortunately there is no fast way for us in Calenco to get our 408 documents to get written to a new server when they're updated. After selecting the new target server for one document, Calenco will immediately regenerate the document and write it to the new server. That slows down the pace at which we can do the same for the other documents: Calenco needs to regenerate and upload 1.2 GB of documentation, during most of that time it will be impossible to select the new target server for another document. As papoteur just said on IRC: "It's possible, but it would take hours or days" So it would be great if docteam.mageia.nl could point to docteam.mageia.org.uk when the latter starts working. _Not_ to mageia.org.uk, because that'll redirect to mageia.org in the future. Btw, mageia.nl is in quarantaine till 2017-11-08 01:54:57 (UTC), unless the former owner releases it before.
I'll happily renew/transfer control of mageia.nl at cost. If desired, just let me know who to transfer the domain to. From my registrar, on .nl domains in quarantine: Quarantine period: After deleting/expiring of a domain of this type, the domain will enter into a quarantine period of 40 days. After this the domain will become available for registration. During the quarantine period, the domain can be restored by us. The costs for this procedure are EUR 20,-. The costs of a quarantined domain transfer are EUR 80,-. All prices displayed, do not include VAT.
€ 80 is more than the € 10 we discussed before the quarantine period, but I guess the € 10 never included a transfer. @ Remmy It doesn't feel good to ask of you to stay involved, after you've helped us so much longer than any of us intended. Or wouldn't it be a problem at all for you if we'd go for the € 20 option? If it would _not_ be a problem, then please let WebConquest renew the domain and tell me the IBAN to transfer the € 20 to. In that case, please make docteam.mageia.nl point to docteam.mageia.org.uk @ all In case the € 20 option can't be used, I don't think we should go for the € 80 option.... but I'm Dutch and very stingy, so feel free to protest :-) _If_ allowed to take a month to do it gradually, then I'm willing to do the needed work to let Calenco write all (re)generated documents to docteam.mageia.org.uk instead of to docteam.mageia.nl (I intend to only adjust the target server for the manuals of one language a day). Doing the hundreds of manuals one after another is no option, because of the huge amount of time lost when waiting for Calenco to regenerate each document and write it to the remote server. http://docteam.mageia.org.uk/ is up and running, btw :-)
(In reply to Marja van Waes from comment #22) > > and tell me the IBAN to transfer > the € 20 to and tell me how much VAT to add to that sum ;-) >
(In reply to Marja van Waes from comment #22) > € 80 is more than the € 10 we discussed before the quarantine period, but I > guess the € 10 never included a transfer. That is because the domain registration expired. Involved parties charge extra during that period to restore things. I can request for the domain to be reinstated, and transfer it at a later date. > _If_ allowed to take a month to do it gradually, then I'm willing to do the > needed work to let Calenco write all (re)generated documents to > docteam.mageia.org.uk instead of to docteam.mageia.nl > http://docteam.mageia.org.uk/ is up and running, btw :-) Would it not be quicker to use sed or similar to do a global replace in all the files?
(In reply to Remco Rijnders from comment #24) > > Would it not be quicker to use sed or similar to do a global replace in all > the files? We don't have access to the files where that information is stored, such files are hidden to us and we can only change them in the web interface of Calenco, one at a time. If there had been a way to work around the web interface to do this faster, then papoteur would have found it.
mageia.nl has been restored and reregistered for 3 more months. Should I point docteam.mageia.nl to the new address, or leave things as they are now? (That is, nothing has been changed on my end but the registration renewed).
(In reply to Remco Rijnders from comment #26) > mageia.nl has been restored and reregistered for 3 more months. Should I > point docteam.mageia.nl to the new address, or leave things as they are now? > (That is, nothing has been changed on my end but the registration renewed). Thanks, Remco :-D please point docteam.mageia.nl to docteam.mageia.org.uk :-)
Thanks Remmy and Marja. There is also a RESTFUL API interface to deal with Calenco content. It's documentation is here: https://doc.neodoc.biz/Calenco-Doc/API/calenco-v23-rest-api-specs.html To update a publication: https://doc.neodoc.biz/Calenco-Doc/API/workspaces-wksp-publications-pub-put.html I presume that you can send the invoice to ennael with IBAN. Will be the subsequent transfer object of an invoice?
CC: (none) => yves.brungard_mageia
Created attachment 9720 [details] Non working script Here is the script in Python I try to use. I can get the list, but changing a parameter in the publication fails each time with "400" error.
DNS has (just) been updated accordingly. Please let me know in case of any issues.
Hello Remmy, For the moment, I get a waiting page from Zen Internet.
(In reply to Remco Rijnders from comment #30) > DNS has (just) been updated accordingly. Please let me know in case of any > issues. (In reply to papoteur from comment #31) > Hello Remmy, > For the moment, I get a waiting page from Zen Internet. I get that page too, when going to 82.71.204.7 Going to http://docteam.mageia.org.uk/ gives the correct page, so does going to http://mageia.potsherds.org/public_html/ (both [sub]domains share the same ip address) Is it possible to point docteam.mageia.nl to docteam.mageia.org.uk instead of to 82.71.204.7 ?
The server is a hosted cPanel instance, so multiple domains on same IP. Must use FQDN or it won't work. Simon
I think this has to be changed on the webserver side of things. I can change DNS to point to CNAME docteam.mageia.org.uk but I think that will only result in the DNS now pointing to docteam.mageia.org.uk DNS instead of directly resolving to the IP. The browser will still ask for docteam.mageia.nl of the server listening on 82.71.204.7 so the end result will be the same.
(In reply to Remco Rijnders from comment #34) > I think this has to be changed on the webserver side of things. I can change > DNS to point to CNAME docteam.mageia.org.uk but I think that will only > result in the DNS now pointing to docteam.mageia.org.uk DNS instead of > directly resolving to the IP. The browser will still ask for > docteam.mageia.nl of the server listening on 82.71.204.7 so the end result > will be the same. Thanks a lot for all your help, Remco. Papoteur managed, with the help of Fabián Mandelbaum, to improve his script and change the target server for all our >400 publications. They do now get written to docteam.mageia.org.uk, so it is OK to let the docteam.nl registration expire. (I'll obsolete this comment and any other comment that our sysadmins won't need when they find time to create a solution within mageia.org)