... | @@ -4,7 +4,7 @@ |
... | @@ -4,7 +4,7 @@ |
|
Here are some of the most frequently asked questions on the new `ohwr.org`
|
|
Here are some of the most frequently asked questions on the new `ohwr.org`
|
|
site.
|
|
site.
|
|
|
|
|
|
### What was communicated via e-mail? Did I miss something?
|
|
## What was communicated via e-mail? Did I miss something?
|
|
|
|
|
|
The messages sent out on Feb 7th 2019 were [a note on the Gitlab
|
|
The messages sent out on Feb 7th 2019 were [a note on the Gitlab
|
|
migration](https://www.ohwr.org/project/ohr-support/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
|
migration](https://www.ohwr.org/project/ohr-support/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
... | @@ -14,7 +14,7 @@ subscribers](https://www.ohwr.org/project/ohr-support/uploads/d82f9d7ce640c31594 |
... | @@ -14,7 +14,7 @@ subscribers](https://www.ohwr.org/project/ohr-support/uploads/d82f9d7ce640c31594 |
|
At the final steps of the migration, `ohwr.org` users were informed throug the following [note](uploads/bff8c0c2a7fb62ce924229c9a05610a8/final-notification-users-ohwr.org.txt) and subscribers to mailing lists were sent [this note](uploads/4a2a7f99c50f399a08cf0a21c41fd805/final-notification-subscribers-ohwr.org)
|
|
At the final steps of the migration, `ohwr.org` users were informed throug the following [note](uploads/bff8c0c2a7fb62ce924229c9a05610a8/final-notification-users-ohwr.org.txt) and subscribers to mailing lists were sent [this note](uploads/4a2a7f99c50f399a08cf0a21c41fd805/final-notification-subscribers-ohwr.org)
|
|
|
|
|
|
|
|
|
|
### Ok, what should I do after the site is migrated?
|
|
## Ok, what should I do after the site is migrated?
|
|
|
|
|
|
Very little. After `ohwr.org` comes back,
|
|
Very little. After `ohwr.org` comes back,
|
|
|
|
|
... | @@ -25,7 +25,8 @@ Very little. After `ohwr.org` comes back, |
... | @@ -25,7 +25,8 @@ Very little. After `ohwr.org` comes back, |
|
registered e-mail address.
|
|
registered e-mail address.
|
|
- that's it
|
|
- that's it
|
|
|
|
|
|
### What happened to mailing lists?
|
|
|
|
|
|
## What happened to mailing lists?
|
|
|
|
|
|
Maintenance of a full mailing list server proved to be extremely costly;
|
|
Maintenance of a full mailing list server proved to be extremely costly;
|
|
we have reduced manpower to keep the site up. After much reflection on
|
|
we have reduced manpower to keep the site up. After much reflection on
|
... | @@ -34,7 +35,8 @@ that setting up a discussion forum would be the best alternative. Not |
... | @@ -34,7 +35,8 @@ that setting up a discussion forum would be the best alternative. Not |
|
much is lost, as you can still receive updates via e-mail by subscribing
|
|
much is lost, as you can still receive updates via e-mail by subscribing
|
|
to topics.
|
|
to topics.
|
|
|
|
|
|
### How can I keep being notified by ohwr.org forums ?
|
|
|
|
|
|
## How can I keep being notified by ohwr.org forums ?
|
|
|
|
|
|
The topic you were subscribed to (for instance, `white-rabbit-dev`) is
|
|
The topic you were subscribed to (for instance, `white-rabbit-dev`) is
|
|
now a **category** within the Discourse space of
|
|
now a **category** within the Discourse space of
|
... | @@ -47,7 +49,7 @@ button. You can select there the amount of notification you will get |
... | @@ -47,7 +49,7 @@ button. You can select there the amount of notification you will get |
|
whenever something is posted in the category.
|
|
whenever something is posted in the category.
|
|
|
|
|
|
|
|
|
|
### What about my mailing list subscriptions? How do I login into `forums.ohwr.org`?
|
|
## What about my mailing list subscriptions? How do I login into `forums.ohwr.org`?
|
|
|
|
|
|
The procedure is really similar to the one described in the above
|
|
The procedure is really similar to the one described in the above
|
|
answer. Your e-mail address (the one you used to subscribe to mailing
|
|
answer. Your e-mail address (the one you used to subscribe to mailing
|
... | @@ -58,7 +60,7 @@ lists) will be already registered in the `forums.ohwr.org` system. |
... | @@ -58,7 +60,7 @@ lists) will be already registered in the `forums.ohwr.org` system. |
|
an e-mail with a password reset link.
|
|
an e-mail with a password reset link.
|
|
- That's all\!
|
|
- That's all\!
|
|
|
|
|
|
### Again: what happened to my subscriptions? I want to get e-mail notifications. What should I do?
|
|
## Again: what happened to my subscriptions? I want to get e-mail notifications. What should I do?
|
|
|
|
|
|
Let us imagine you want to get notifications about the category `white-rabbit-dev`. The steps are very simple:
|
|
Let us imagine you want to get notifications about the category `white-rabbit-dev`. The steps are very simple:
|
|
|
|
|
... | @@ -66,7 +68,7 @@ Let us imagine you want to get notifications about the category `white-rabbit-de |
... | @@ -66,7 +68,7 @@ Let us imagine you want to get notifications about the category `white-rabbit-de |
|
- Note the subscription button at the top right of the page (see the [attached screenshot](uploads/7d248853c22862269bee94f4acaab5fa/subscription-button.png))
|
|
- Note the subscription button at the top right of the page (see the [attached screenshot](uploads/7d248853c22862269bee94f4acaab5fa/subscription-button.png))
|
|
- There, you can select the level of notification intrusiveness with which you want to be notified by e-mail
|
|
- There, you can select the level of notification intrusiveness with which you want to be notified by e-mail
|
|
|
|
|
|
### What happened to my Git repository references?
|
|
## What happened to my Git repository references?
|
|
|
|
|
|
Git repository reference URLs have changed, as it is not possible to keep them as they were in the former platform.
|
|
Git repository reference URLs have changed, as it is not possible to keep them as they were in the former platform.
|
|
This implies that you will be submitted to the (hpefully minor) inconvenience of changing remote references in
|
|
This implies that you will be submitted to the (hpefully minor) inconvenience of changing remote references in
|
... | @@ -102,7 +104,7 @@ origin https://ohwr.org/project/spec-sw.git (fetch) |
... | @@ -102,7 +104,7 @@ origin https://ohwr.org/project/spec-sw.git (fetch) |
|
origin https://ohwr.org/project/spec-sw.git (push)
|
|
origin https://ohwr.org/project/spec-sw.git (push)
|
|
```
|
|
```
|
|
|
|
|
|
### What about submodules and submodule references?
|
|
## What about submodules and submodule references?
|
|
|
|
|
|
If you use submodules, you deserve what you get :smile:.
|
|
If you use submodules, you deserve what you get :smile:.
|
|
|
|
|
... | @@ -128,7 +130,7 @@ $ git commit -m "update of submodule URLs after OHWR migration" |
... | @@ -128,7 +130,7 @@ $ git commit -m "update of submodule URLs after OHWR migration" |
|
|
|
|
|
You might experience this problem when using old version of GIT and trying to access ohwr.org repository via HTTPS. If this happens, you need to update your git version. We experienced this problem with git 1.9.1 while all works fine with 2.7.4.
|
|
You might experience this problem when using old version of GIT and trying to access ohwr.org repository via HTTPS. If this happens, you need to update your git version. We experienced this problem with git 1.9.1 while all works fine with 2.7.4.
|
|
|
|
|
|
### My project looks **weird** and empty. Where's my stuff?
|
|
## My project looks **weird** and empty. Where's my stuff?
|
|
|
|
|
|
First of all, check the URL. After the migration, the hierarchical URLs of the old site were flattened. So, your project URL should look like
|
|
First of all, check the URL. After the migration, the hierarchical URLs of the old site were flattened. So, your project URL should look like
|
|
https://ohwr.org/project/fmc-adc-400k18b4cha-iso
|
|
https://ohwr.org/project/fmc-adc-400k18b4cha-iso
|
... | @@ -139,7 +141,17 @@ with hierarchical information in the middle. |
... | @@ -139,7 +141,17 @@ with hierarchical information in the middle. |
|
The first URL is the correct one, and your project and stuff is there, alive and kicking.
|
|
The first URL is the correct one, and your project and stuff is there, alive and kicking.
|
|
The latter, although **is** an existent URL/project, is there only to keep old submodule URLs, and might eventually disappear.
|
|
The latter, although **is** an existent URL/project, is there only to keep old submodule URLs, and might eventually disappear.
|
|
|
|
|
|
### When editing a wiki page, my attempt at attaching a file is rejected with a **Forbidden 403 try again or another file** error. What can I do?
|
|
## When editing a wiki page, my attempt at attaching a file is rejected with a **Forbidden 403 try again or another file** error. What can I do?
|
|
|
|
|
|
|
|
This is a nasty one that we get quite often. There are different things you can try, and we're sorry that we have not yet found a sure way yet.
|
|
|
|
|
|
|
|
### Try logging in to ohwr.org instead of www.ohwr.org
|
|
|
|
|
|
|
|
I was logged in at [www.ohwr.org](http://www.ohwr.org) and there it failed. I revoked all sessions, went out of the browser, went back and it still failed.
|
|
|
|
|
|
|
|
Then I logged in to [ohwr.org](http://ohwr.org), not [www.ohwr.org](http://www.ohwr.org) and it works like a charm!
|
|
|
|
|
|
|
|
### Try removing old active sessions and authentication tokens
|
|
|
|
|
|
This is a bug related to authentication tokens in the framework that the current Gitlab version is based on. For the full technical story, you may visit issue [253](https://ohwr.org/project/ohr-support/issues/253). But to get this fixed for you, try the following first:
|
|
This is a bug related to authentication tokens in the framework that the current Gitlab version is based on. For the full technical story, you may visit issue [253](https://ohwr.org/project/ohr-support/issues/253). But to get this fixed for you, try the following first:
|
|
|
|
|
... | @@ -152,8 +164,11 @@ This is a bug related to authentication tokens in the framework that the current |
... | @@ -152,8 +164,11 @@ This is a bug related to authentication tokens in the framework that the current |
|
|
|
|
|
If this procedure fixes the problem for you, congratulations.
|
|
If this procedure fixes the problem for you, congratulations.
|
|
|
|
|
|
|
|
### Ask the maintainers to reboot the GitLab server
|
|
For some users, the issue seems to be more persistent. The next step would be to ask the maintainers (`ohwr-support@cern.ch`) a restart of the Gitlab server; this drastic action seems to have cured the problem of some users. Although this cannot be done on a regular basis, it is worth trying if the above recipe did not work.
|
|
For some users, the issue seems to be more persistent. The next step would be to ask the maintainers (`ohwr-support@cern.ch`) a restart of the Gitlab server; this drastic action seems to have cured the problem of some users. Although this cannot be done on a regular basis, it is worth trying if the above recipe did not work.
|
|
|
|
|
|
|
|
### Upload your file with a Python script
|
|
|
|
|
|
If nothing of the above worked, a workaround is still possible. You will use a Python script that uploads a file by talking directly to `ohwr.org` via its API, thus bypassing the web interface. You will need a Python installation with the `requests` package installed.
|
|
If nothing of the above worked, a workaround is still possible. You will use a Python script that uploads a file by talking directly to `ohwr.org` via its API, thus bypassing the web interface. You will need a Python installation with the `requests` package installed.
|
|
|
|
|
|
The [attach](https://ohwr.org/project/ohr-support/uploads/20ed6f14cd251069034061fdd6600d7e/attach) script is quoted in [the comment to issue 253](https://ohwr.org/project/ohr-support/issues/253#note_113258) that introduces this technique. It requires you to provide a so-called *personal access token*, which is simply a cryptographic key that identifies you to the server, allowing you to make API calls.
|
|
The [attach](https://ohwr.org/project/ohr-support/uploads/20ed6f14cd251069034061fdd6600d7e/attach) script is quoted in [the comment to issue 253](https://ohwr.org/project/ohr-support/issues/253#note_113258) that introduces this technique. It requires you to provide a so-called *personal access token*, which is simply a cryptographic key that identifies you to the server, allowing you to make API calls.
|
... | @@ -178,7 +193,9 @@ and paste the text that the program prints in your wiki page to link to the just |
... | @@ -178,7 +193,9 @@ and paste the text that the program prints in your wiki page to link to the just |
|
|
|
|
|
This **must** work, as it does not rely on the clever authentication verification of Ruby on Rails.
|
|
This **must** work, as it does not rely on the clever authentication verification of Ruby on Rails.
|
|
|
|
|
|
### Files
|
|
---
|
|
|
|
|
|
|
|
## Files
|
|
* [notification-users-ohwr.org](/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
|
* [notification-users-ohwr.org](/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
|
* [notification-subscribers-ohwr.org](/uploads/d82f9d7ce640c31594fd75596dcb1693/notification-subscribers-ohwr.org)
|
|
* [notification-subscribers-ohwr.org](/uploads/d82f9d7ce640c31594fd75596dcb1693/notification-subscribers-ohwr.org)
|
|
* [subscription-button.png](/uploads/54c414e32c2a86676727cd3f07c112e8/subscription-button.png)
|
|
* [subscription-button.png](/uploads/54c414e32c2a86676727cd3f07c112e8/subscription-button.png)
|
... | | ... | |