Editing CommunityData:Etherpad

From CommunityData

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 6: Line 6:


You can make a semi-private one by including the word "private" in front of the pad name. For example, if you name your pad <code>private-cdsc_cabal_meeting-20380119</code> people will be asked for a username and password shared with the group. You can ask other folks in the group for the username or password or you can find by searching the [[CommunityData:Email#Email Lists|email list]] archives for the '''collective-XXXX@communitydata.science''' email lists.
You can make a semi-private one by including the word "private" in front of the pad name. For example, if you name your pad <code>private-cdsc_cabal_meeting-20380119</code> people will be asked for a username and password shared with the group. You can ask other folks in the group for the username or password or you can find by searching the [[CommunityData:Email#Email Lists|email list]] archives for the '''collective-XXXX@communitydata.science''' email lists.
== Backing up Etherpads ==
Etherpads should not be treated as long term storage. Although we have no plan to purge things from our own server, there's no promise that they will be kept across upgrades and server migrations either. As a result, we have a system to backup our Etherpads. It runs once a days and keeps a backup copy each day. We can use the backups to go back to any old copy of any Etherpad so you can safely blow away old text and know you will be able to get the archived text back if you need it.
That said, we need to register every Etherpad that we want backed up first. To do that, we need to first check out <code>cdsc-etherpads</code> repository from the [[CommunityData:Git|group Git repository]] with a line in your terminal like:
<syntaxhighlight lang='bash'>
git clone git@code.communitydata.science:cdsc-etherpads
</syntaxhighlight>
If you get a permission denied errors, follow the instructions on [[CommunityData:Git]] to get setup to use the CDSC git repository.
To start backing up a new Git repository, you should add a new line to the bottom of <code>ETHERPAD_URLS</code>. The lines should look like:
<syntaxhighlight lang='bash'>
http://etherpad.communitydata.science/p/cdsc_cabal_meeting-20380119 # meeting notes from the winter 2038 cabal meeting
</syntaxhighlight>
As you can see, comments following <code>#</code> are supported in the file. They are not required.
The complete workflow should look like:
<syntaxhighlight lang='bash'>
git clone git@code.communitydata.science:cdsc-etherpads
cd cdsc-etherpads
vim ETHERPAD_URLS # or whatever your preferred editor is!
##### EDIT TO ADD NEW URL #######
git add ETHERPAD_URLS
git commit -m 'added new cabal URL'
git push
</syntaxhighlight>


== Administration for Etherpad ==
== Administration for Etherpad ==
Line 42: Line 74:
<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>
systemctl restart etherpad
systemctl restart etherpad
</syntaxhighlight>
== Backing up Etherpads (optional/deprecated) ==
{{notice|This is entirely optional and is probably no longer necessary since we moved to our own Etherpad server.}}
Etherpads should not be treated as long term storage. Although we have no plan to purge things from our own server, there's no promise that they will be kept across upgrades and server migrations either. As a result, we have a system to backup our Etherpads. It runs once a days and keeps a backup copy each day. We can use the backups to go back to any old copy of any Etherpad so you can safely blow away old text and know you will be able to get the archived text back if you need it.
That said, we need to register every Etherpad that we want backed up first. To do that, we need to first check out <code>cdsc-etherpads</code> repository from the [[CommunityData:Git|group Git repository]] with a line in your terminal like:
<syntaxhighlight lang='bash'>
git clone git@code.communitydata.science:cdsc-etherpads
</syntaxhighlight>
If you get a permission denied errors, follow the instructions on [[CommunityData:Git]] to get setup to use the CDSC git repository.
To start backing up a new Git repository, you should add a new line to the bottom of <code>ETHERPAD_URLS</code>. The lines should look like:
<syntaxhighlight lang='bash'>
http://etherpad.communitydata.science/p/cdsc_cabal_meeting-20380119 # meeting notes from the winter 2038 cabal meeting
</syntaxhighlight>
As you can see, comments following <code>#</code> are supported in the file. They are not required.
The complete workflow should look like:
<syntaxhighlight lang='bash'>
git clone git@code.communitydata.science:cdsc-etherpads
cd cdsc-etherpads
vim ETHERPAD_URLS # or whatever your preferred editor is!
##### EDIT TO ADD NEW URL #######
git add ETHERPAD_URLS
git commit -m 'added new cabal URL'
git push
</syntaxhighlight>
</syntaxhighlight>
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)

Template used on this page: