faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <Blacksmoke16> https://github.com/amberframework/amber/issues/941 that concern was brought up before
<FromGitter> <Blacksmoke16> I'm not core member/close follower but it seems work is being done, just at a slow pace, ref https://github.com/amberframework/amber/compare/v0.35.0...master
<FromGitter> <Blacksmoke16> Not to dis Amber or anything but it may be worth at least looking into alternatives as there are quite a few frameworks these days that didn't exist back then. I'd at least be aware of whats out there even if you dont intend on switching
<FromGitter> <Blacksmoke16> either way Amber is still considered one of the more popular frameworks. I haven't heard/doubt there is any talk about discontinuing it
<FromGitter> <Blacksmoke16> \cc @rukkiddo
<FromGitter> <rukkiddo> thank you for the answer @Blacksmoke16
<FromGitter> <rukkiddo> I tried to followed the official website documentation in order to setup my database again, as I see document is not up-to-date. Also we have deprecated warning for YAML when building the project.
<FromGitter> <rukkiddo> I've never tried to contribute an open source project before but I will see what I can do to help these points. Because I really liked crystal & amber. I hope it will be more active.
<FromGitter> <Blacksmoke16> whats the yaml warning about?
<FromGitter> <rukkiddo> I couldn't reproduced it now, it was related to using YAML.mapping instead of YAML::Serializable
<FromGitter> <rukkiddo> you may say maybe my packages are not up to date but there are still YAML.mapping code in lib folder of my project (I newly built this folder, it was gitignore when I first pull)
<FromGitter> <Blacksmoke16> what crystal version are you on?
<FromGitter> <Blacksmoke16> also be sure to `shards update`
<FromGitter> <rukkiddo> $ crystal -v ⏎ Crystal 0.35.1 (2020-10-17) ⏎ ⏎ LLVM: 10.0.1 ⏎ Default target: x86_64-pc-linux-gnu [https://gitter.im/amberframework/amber?at=5fe03c0c97312f4b6bdebddf]
<FromGitter> <rukkiddo> first I made shards update, then I deleted lib folder and shards.lock & removed all versions from shards.yml then shards install again. you know to make sure
<FromGitter> <Blacksmoke16> https://github.com/amberframework/amber/pull/1210 looks like that was fixed/released in amber 0.35.0
<FromGitter> <Blacksmoke16> could have been a cache thing or some other lib? :shrug:
<FromGitter> <rukkiddo> under lib/amber/src/amber/cli/config.cr, I will check it from github
<FromGitter> <Blacksmoke16> actually i think its because next crystal version hasnt been released yet
<FromGitter> <rukkiddo> yeah maybe
_whitelogger has joined #amber
_whitelogger has joined #amber
_whitelogger has joined #amber
<FromGitter> <damianham> I recently had a problem with hackers trying to break into my server - the result of which was to cause the service to fail as it ran out of database connections. I have since taken measures to address this at the nginx level but I think there maybe some things that Amber/Granite could do to mitigate the effects of these kind of attacks. Principally, if the route would return a 404, which is the result for most
<FromGitter> ... attempts - a database connection should not be opened. What I have done is prefixed all my routes with a version identifier and only pass those requests that match the prefix through to the Amber instance so nginx returns a 404 on any request that does not match the prefix or a static file. Does anyone have any thou ... [https://gitter.im/amberframework/amber?at=5fe0c55363fe0344960e3323]
feepbot has quit [Ping timeout: 246 seconds]
feepbot has joined #amber
o5r has joined #amber
<FromGitter> <rukkiddo> I try amber's docker for the first time: ⏎ $ amber new server ⏎ $ cd test ⏎ $ sudo docker build -t server:v1 . ⏎ Unable to satisfy the following requirements: ... [https://gitter.im/amberframework/amber?at=5fe11fbbac9d8e7463c3b98b]
<FromGitter> <rukkiddo> am I missing something?
<FromGitter> <rukkiddo> I try amber's docker for the first time: ⏎ $ amber new server ⏎ $ cd server ⏎ $ sudo docker build -t server:v1 . ⏎ Unable to satisfy the following requirements: ... [https://gitter.im/amberframework/amber?at=5fe1201cc746c6431ccb463e]
<FromGitter> <rukkiddo> docker-compose up gives the same result btw
<FromGitter> <rukkiddo> I just updated the default dockerfile, added these lines after workdir and it worked fine ⏎ ⏎ RUN apt -y update ⏎ RUN apt -y install crystal ⏎ ... [https://gitter.im/amberframework/amber?at=5fe12b1263fe0344960f5147]
<FromGitter> <rukkiddo> because I wouldn't expect something like this to be missing
<FromGitter> <Blacksmoke16> lol what
<FromGitter> <Blacksmoke16> that makes no sense
<FromGitter> <Blacksmoke16> https://github.com/amberframework/amber/blob/master/Dockerfile#L1 its based off the crystal image?
<FromGitter> <rukkiddo> ikr: ⏎ FROM amberframework/amber:0.35.0 ⏎ ⏎ WORKDIR /app ⏎ ... [https://gitter.im/amberframework/amber?at=5fe12d05aa6bb528c363f56c]
<FromGitter> <rukkiddo> I added the apt part, it didn't work without it
<FromGitter> <rukkiddo> I tried to create project from scratch still had the same problem
<FromGitter> <Blacksmoke16> oh wait, this is the dockerfile that gets created when you start a new project
<FromGitter> <rukkiddo> yeah
<FromGitter> <Blacksmoke16> nvm then, i was looking at the one in the actual repo