Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promote muon #10

Open
paneq opened this issue Jan 13, 2013 · 8 comments
Open

Promote muon #10

paneq opened this issue Jan 13, 2013 · 8 comments

Comments

@paneq
Copy link
Member

paneq commented Jan 13, 2013

Write blogpost or record video on how to use muon daily.

@jdudek
Copy link
Member

jdudek commented Jan 13, 2013

Thanks for submitting this issue. I like the idea of recording a video. I'm also thinking about a lightning talk at DRUG at some point.

However, I don't want to encourage people to use muon yet, at least not until database format stabilizes. I have some ideas that will totally break backwards compatibility... let's wait a little...

@paneq
Copy link
Member Author

paneq commented Jan 13, 2013

You worry too much. Writing migrations is easy :) Talk about those ideas at @drugpl . Get feedback early :)

@paneq
Copy link
Member Author

paneq commented Jan 13, 2013

Here is my idea to you: Set yourself a deadline for wroc_love.rb lightning talk :)

@jdudek
Copy link
Member

jdudek commented Jan 13, 2013

Yeah, I was thinking about wroc_love.rb too ;-)

Now I should spend more time coding than talking about muon future...

@paneq
Copy link
Member Author

paneq commented Jan 15, 2013

What is your idea for db format. I think YAML serialized would be uber simple. However if you wish to transfer it to remote host (ex to store and compute stats) then it would be dangerous (aka recent rails security problems). So i think maybe JSON ? It would be good imho for freestyle key:value pairs. What do you think ?

@jdudek
Copy link
Member

jdudek commented Jan 15, 2013

The idea is to use Git as the database (similar to git-notes), which gives us pushes for free and is funny (imagine muon rebase). You may want to check gitdb branch.

@paneq
Copy link
Member Author

paneq commented Jan 15, 2013

I know that you want to use Git as database and it sounds cool. Just wondering about what to store inside of it?

Currently we store things like 2013-01-14 23:16:50 +0100,2013-01-15 00:11:20 +0100. Instead i would prefer having JSON or YAML stored inside git.

@jdudek
Copy link
Member

jdudek commented Jan 15, 2013

Aa, ok ;) I don't know yet. Either some simple text format or JSON/YAML. I'd like to have human-editable messages and JSON is not perfect for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants