Chat-Ops integration with Wiki

[marceloschmidt]

It would be cool to have an integration with Github/Gitlab Wiki, or an internal wiki, for storing .md files related to the room and being able to edit them on-the-fly.
Displaying items in a tree-like structure would be good too.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[f4llc0nn]

Great :)
A multi-user editing mechanism for .md files in a room would increase a lot of our productivity, keeping workflow entirely on rocket.chat.

Example: We can use it to keep important project's info/files direct on a project channel and update this documentation in the channel. A tree-like structure would even enhance this experience.

[Sing-Li]

JavaScript source file edit would be awesome (although not quite what the title suggests) !

Multi-user shared edit as per @fallc0nn ? or Private per-user? Very different use cases.

Also, how will we 'delegate' the identity? What if the user did not oauth'd in via GitHub or GitLab - no identity for write on that system?

[f4llc0nn]

"Multi-user shared edit as per @fallc0nn ? or Private per-user? Very different use cases."

I'm thinking more simple for now. Not simultaneous editing.

Imagine this scenario:

• A technical project internal group with 5 analysts.
• Analyst Refactored and reorganised entire css/less files and logic. #1 creates a .md file with procedures, snippet codes from conf files etc.
• One week later, Analyst implemented new page-loader animated icon #2 updated one of the conf files and wants to update the .md main file created by Analyst Refactored and reorganised entire css/less files and logic. #1.
• Two months later, Analyst Language options #6 joined company and wants to read and update the .md file to make more verbose. He separates the original .md file in four .md files: "conf_files.md", "architecture.md", "contact_info.md" and "project_info.md", put all in a tree-like structure under "md" directory.
• Analyst Internal server error after github auth #4 creates a "img" directory with Visio-like images of the architecture.

And so on.

tl;dr
What I'm aiming for is a limited (but useful+productive) way to keep collaborative files from projects into a project/activity room.

[Sing-Li]

So ...

• a managed collection of .md files associated with each channel; using current upload file storage is probably fine
• a markdown renderer and editor for these files
• a file manager to access these files
• the two bullets above can be combined if we find a JS embeddable wiki-in-a-window

[f4llc0nn]

Yeah, perfect.
To address this issue today, we use a few markdown messages in the channel that only the administrator can edit, and everybody pinned to quickly keep track of last edit.

I think this request can be useful not only for us but for all.

[haceru]

If I may join the conversation, this feature would be extremely useful for collaborative document editing too (for example a procedure or a legislative proposal with multiple editors). If at the end you could export the result as a PDF for example, it would be awesome !

[engelgabriel]

Relates on #2426

[engelgabriel]

Please see initial documentation at https://github.com/RocketChat/Rocket.Chat/wiki/WebHook-Scripting---GitHub

[geekgonecrazy]

@marceloschmidt now that we've moved over to the docs repo, what would that leave us needing to do?

[marceloschmidt]

The original request was for a package or tabbar plugin that would allow for editing on-the-fly. So I think the request is still pending :)

[geekgonecrazy]

Let the chatops thinking begin! I can see this being very easily done with the in band message PR I need to finish up.

[B-Stefan]

Maybe this is interesting for you.
To add your own fly in panel I developed a docker container that pulls the RocketChat source code and generates a new build of RocketChat with your custom meteor module.

This is highly experimental and not production ready

https://github.com/B-Stefan/Sofia/tree/master/service-rocket-chat