draft for fixing #56 #257
draft for fixing #56 #257
Conversation
abizer
requested review from
chriskuehl,
jvperrin,
kpengboy,
matthew-mcallister and
daradib
|
good point |
ocfweb/docs/docs/services/web.md
Outdated
| [contact the university](https://offsitehosting.berkeley.edu/) directly | ||
| to request permission. This is primarily relevant to student groups. | ||
| Similarly, the OCF does not generally allow hosting under custom domain | ||
| names. This means we do not support things like "you_or_your_group.com" |
There was a problem hiding this comment.
This is not entirely true, at least we host a few of these non-berkeley.edu domains and we have a paragraph about hosting without a berkeley.edu subdomain, although given that regular subdomains require an application anyway, I think that could be revised to essentially say only the second point that says we don't pay for the domain, the group wanting to host with us does.
I think we need a clearer policy on what to do about these, and I don't see a problem with the OCF hosting them as long as they follow our requirements.
| #### Off-site hosting | ||
|
|
||
| One question that often comes up is if the OCF is able to host websites | ||
| from services such as Squarespace, Wix, Weebly, Tumblr, etc. Unfortunately |
There was a problem hiding this comment.
I think it should be made clear here that we can host websites imported from these services, but that we don't have the same editing interfaces and stuff that they do. We also can't somehow host a website also hosted by them, that doesn't make any sense, which is more the point you made in the next paragraph.
ocfweb/docs/docs/services/web.md
Outdated
| subsequently charging users to host those sites. This means providing the | ||
| servers, storage space, internet connection, and configurations to allow | ||
| these sites to show up on the internet. Obviously, the OCF is unable to | ||
| access these proprietary backends and is therefore unable to host sites |
There was a problem hiding this comment.
Using the word backend will not make a lot of sense to most people wanting to host with us, maybe just use something like access this proprietary software instead?
|
relevant: rt#6018 |
|
@jvperrin @kpengboy @matthew-mcallister any thoughts? |
| of sources, and must be configured to respond to web requests to the domain | ||
| name in question. While the OCF provides both, only a limited subset of their | ||
| functionality are available for general use by the campus community due to the | ||
| legal, technical, and policy considerations explained above. |
There was a problem hiding this comment.
I feel like this last part doesn't work so well, like the part about the server being "purchased from any variety of sources" and then explaining the limited functionality of our servers. To me, it seems like something we shouldn't be explaining (in vague terms anyway) and something that just complicates the topic.
| servers. However, we may agree to host websites under custom domains on a | ||
| case-by-case basis, usually for University affiliates such as faculty members, | ||
| ASUC/University programs, and others. Please [[contact us|doc contact]] for | ||
| more information. |
There was a problem hiding this comment.
We'd want to link to the vhost policy we are writing for a lot of this part, so I think it might be good if this waits until that is written up, which should be in the next week.
| developed using them. However, the OCF is capable of hosting anything made | ||
| using the free and open-source backends we support, including Wordpress, | ||
| Django, Ruby on Rails, Node.js, PHP, and others. You may wish to consider | ||
| building your website with those if you desire to host with the OCF. |
There was a problem hiding this comment.
I like this section, maybe mention the ability to export from those providers though in case they are already using them? I would make sure to discourage exporting from their service and importing to the OCF though because that complicates setting up their site and probably wouldn't be as easy to maintain due to whatever obfuscation/plugins they use or other stuff like that (unless it's simpler, like migrating from Wordpress.com to Wordpress at the OCF, which we already have a docs section for).
| using a proprietary service to allow users to design their websites, and | ||
| subsequently charge users to host those sites. This means providing the | ||
| servers, storage space, internet connection, and configurations to allow | ||
| these sites to show up on the internet. Obviously, the OCF is unable to |
| @@ -11,6 +11,52 @@ where `user` is the account name. | |||
| Group accounts may also request a [[virtual host|doc services/vhost]] for | |||
| another domain (e.g., group.berkeley.edu). | |||
|
|
|||
| #### Off-site hosting | |||
There was a problem hiding this comment.
Can we put most of this information somewhere else? A small section here that links to another page might work well. Right now this takes a page which contains useful technical information about updating your website and inserts a giant blob of political text which isn't relevant to most people.
draft, obviously. Any thoughts?