Show HN: CMS Server written in Go (alpha)

http://www.bytengine.com

by wilsonfiifi • 13 years ago

61 33 13 years ago

wilsonfiifi12• 13 years ago

Still needs quite a bit more documentation, code comments, architecture revisions etc... your suggestions/comments/feedback are most welcome.

cheers

tuananh• 13 years ago

I read the domain as 'By tengine'. Does it has anything to do with tengine web server?

ConceitedCode• 13 years ago

I read it as ByteEngine at first glance. Maybe it shares an E?

wilsonfiifi12• 13 years ago

yes the e from byte & engine are fused :-)

shadowmint• 13 years ago

mongodb + redis instead of sql? ...because?

wilsonfiifi12• 13 years ago

IMO Mongodb makes it easier to add and query file metadata and Redis is really just for session info.

dualogy3• 13 years ago

Don't get it. You already have a Mongo, why also use Redis just for that? I mean your Mongo is in-memory too. Or do you anticipate a larger-than-RAM dataset for the MongoDB?

ExpiredLink• 13 years ago

... because it's web scale.

pjmlp• 13 years ago

... because it is what the cool kids use instead of what the boring enterprise guys are using.

FraaJad• 13 years ago

because i don't care for errors on `random(x)/2` occasions.

mappu2• 13 years ago

> Password must be composed of only alpha-numeric characters.

Okay, why?

This caught my eye so i had a look through auth.go. Passwords are salted sha1... okay, but why not bcrypt? No PBKDF2? No field for hash format versioning if you want to backwards-compatible upgrade to bcrypt in future? Guess you could always go by the salt length or something.

It looks like your code to hash the password and salt is copy-pasted and appears twice, don't do that.

Your salts are 16 random bytes, okay.. but why base64 encode the salt before hashing? Now some structure of the content is known that might expose a weakness.

wilsonfiifi12• 13 years ago

:-) put me on the spot! thanks for going through the code though.

security layer definitely needs more work. my choices were mostly limited by my haste to get a working prototype and not very well thought through.

mappu2• 13 years ago

No problem, thanks for sharing your project with everyone! Just people definitely like to use symbols in passwords.

Your fundamentals are fine, i don't think those are very serious problems compared to the average custom web app in the wild (most of which probably use plaintext passwords with no concern for sqli or xss...)

xSwag2• 13 years ago

Weird headers

The main page is active in the browser but the header says 404 Not Found, maybe it's a bug?

  ~$ curl -IL http://www.bytengine.com/    
  HTTP/1.1 404 Not Found
  Server: nginx/1.1.19

    
  ~$ curl -IL http://www.bytengine.com/should_404    
  HTTP/1.1 404 Not Found
  Server: nginx/1.1.19

wilsonfiifi12• 13 years ago

must probably be an issue with my nginx config and the proxying. will have a look at it. thanks

xSwag2• 13 years ago

Yeah, just thought I'd point it out because it will cause issues with spiders.

the1• 13 years ago

what's wrong with webdav?

wilsonfiifi12• 13 years ago

can you elaborate further

klibertp• 13 years ago

I think that all that's wrong with alternatives to this kind of projects is that they are not written by the author. It's ok actually, many people and many great technologies started as pet projects; it just means that asking questions like this makes no sense :)

reedlaw• 13 years ago

I'm having trouble understanding the motivation or use case. The documentation gives examples of logging in, creating filesystem-like structures, and uploading files. How is this an improvement upon a regular filesystem and scp/sftp? I do like the web console though.

dualogy3• 13 years ago

Well, from the docs:

Therefore, instead of dealing with key-values, objects ids and primary keys, you can access your data using file paths just as you would with a regular file system. Bytengine’s file system is modelled on the linux file system where you have a root directory ‘/’ and file paths separated by a forward slash ‘/’. Bytengine stores your content in Files that can further be organised in Directories.

So there you have it! Wait...

wilsonfiifi12• 13 years ago

Appart from being able to access your content as you would a regular file system, you can also query and modify your content metadata.

So you could upload pictures, tag them in JSON and later run live queries based on the tags from your client app (to sort them based on location for example).

I'll be adding more/better docs in the coming days.

cheers

ams6110• 13 years ago

How is this an improvement upon a regular filesystem and scp/sftp

scp/sftp is great, but if you've ever had to deal with large numbers of users trying to properly manage ssh key pairs you will know it's not an approach that will work at scale.

garysweaver• 13 years ago

neat. is this a bug?

server.newuser

line[1]: expected string in New User; got EOF

wilsonfiifi12• 13 years ago

Hi! please run: 'help server.newuser' to check the syntax.

cheers

Show HN: CMS Server written in Go (alpha)

Related Stories