Manuals down....who to tell?


#1

I’m pretty new to Rails, so still trying to find my way around. I’ve
been trying to access manuals.rubyonrails.com for several days now but
am getting a 503 error.

Could anyone enlighten me as to where on looks for “service outage” or
other status messages for rubyonrails.com and subdomains? I can’t find
anything that would show that whoever administers the manuals knows it
is down, or is doing anything about it.

Thanks
gt_sdi


#2

it’s a continual problem. try http://www.railsmanual.org

ed


#3

Thanks for the reply…I wish railsmanual.org helped…it’s great for
api docs…but was looking for something more “tutorial” in
nature…in particular the manual on testing file uploadsl, as I’m
trying to figure out how to unit test a file upload.

gt_sdi


#4

Like you, I haven’t been able to find anyone who can help with this so
I’ve raised a ticket (#7601: How can we make manuals.rubyonrails.com
available reliably?). Hopefully that will get the attention of
someone in the core team.

Keith


#5

Rick,

Like you, I haven’t been able to find anyone who can help with this so
I’ve raised a ticket (#7601: How can we makemanuals.rubyonrails.com
available reliably?). Hopefully that will get the attention of
someone in the core team.

I have a Mephisto instance set up. Let me know if you’d like to help
port the content over frommanualssite. I’m trying to consolidate
the various apps that we have to babysit. I’m currently working on
the Rails homepage.

Firstly, is that why the manuals site is down? I don’t see why it has
to be down to enable content to be ported across.

If the core Rails team have decided to use Mephisto, what’s involved
in helping to port the content? Also, is Jamis B. aware that the
consolidation to Mephisto includes the manuals? I notice he and
others have had some recent (inconclusive) discussion about the best
way to maintain the Capistrano documentation.

Sorry to bombard you with these questions. I’d like a better
understanding of what the direction is and what’s involved before I
commit to taking on a task.

Regards,
Keith


#6

On 2/20/07, Keith P. removed_email_address@domain.invalid wrote:

Like you, I haven’t been able to find anyone who can help with this so
I’ve raised a ticket (#7601: How can we make manuals.rubyonrails.com
available reliably?). Hopefully that will get the attention of
someone in the core team.

I have a Mephisto instance set up. Let me know if you’d like to help
port the content over from manuals site. I’m trying to consolidate
the various apps that we have to babysit. I’m currently working on
the Rails homepage.


Rick O.
http://weblog.techno-weenie.net
http://mephistoblog.com


#7

Firstly, is that why the manuals site is down? I don’t see why it has
to be down to enable content to be ported across.

It’s not a particularly stable app. The server is pretty old and has
a lot of stuff running on it too. There are plans to move it to a
container like the recent trac/svn move, but it’s not near as urgent a
need right now.

If the core Rails team have decided to use Mephisto, what’s involved
in helping to port the content? Also, is Jamis B. aware that the
consolidation to Mephisto includes the manuals? I notice he and
others have had some recent (inconclusive) discussion about the best
way to maintain the Capistrano documentation.

Yup, he’s aware. I don’t think his plans include the manuals site. I
spoke with one of the new authors involved with the Caboose
documentation project, and he mentioned wanting a place to put updated
rails docs. So, we may see a re-org real soon anyway.


Rick O.
http://weblog.techno-weenie.net
http://mephistoblog.com


#8

So, what’s involved in “porting”? Re-writing code? Copying content?

b

Rick O. wrote:

I have a Mephisto instance set up. Let me know if you’d like to help
port the content over from manuals site. I’m trying to consolidate
the various apps that we have to babysit. I’m currently working on
the Rails homepage.


#9

Hi Rick

As per Ben’s question…can you give us an idea of what you need done.
I would welcome an opportunity to contribute to the Rails community,
but should make sure I can follow through on any commitments I make.
Also a little confused (actually that’s mostly a permanent state) as
to whether you saw this as potentially overlapping caboose.

Thanks
GT


#10

On 2/20/07, gt_sdi removed_email_address@domain.invalid wrote:

Hi Rick

As per Ben’s question…can you give us an idea of what you need done.
I would welcome an opportunity to contribute to the Rails community,
but should make sure I can follow through on any commitments I make.
Also a little confused (actually that’s mostly a permanent state) as
to whether you saw this as potentially overlapping caboose.

The caboose documentation project will be contributing back to Rails
directly. So, if they (or anyone really), wanted to add some good
rails manuals, manuals.ror.org is the place for it. As for what’s
involved with porting, just moving content over. I’m moving it to
Mephisto, so you’ll have the full power of that at your disposal.
Right now, I’m thinking of dumping the current set of articles into a
really simplified layout that matches the current ror design. If
someone has any ideas, bring them up.


Rick O.
http://weblog.techno-weenie.net
http://mephistoblog.com


#11

FYI:

http://web.archive.org/web/20060526132936/http://manuals.rubyonrails.org/

has some of the original content.

Keith


#12

On 2/23/07, KJH removed_email_address@domain.invalid wrote:

FYI:

http://web.archive.org/web/20060526132936/http://manuals.rubyonrails.org/

has some of the original content.

I’ve been bringing it back, but it keeps crashing, hence the move to
Mephisto. If anyone knows Mephisto pretty well and has some time this
weekend, let me know. Otherwise, I’ll just do a quick migration so we
don’t have these issues next week.


Rick O.
http://weblog.techno-weenie.net
http://mephistoblog.com