Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 18 2020 19:48
    PatrickSachs commented #100
  • Nov 18 2020 19:48
    PatrickSachs commented #100
  • Nov 18 2020 19:48
    PatrickSachs commented #100
  • Nov 18 2020 00:18
    YellowApple commented #100
  • Nov 17 2020 20:58
    PatrickSachs closed #100
  • Nov 17 2020 20:58
    PatrickSachs commented #100
  • Nov 13 2020 06:15
    YellowApple commented #100
  • Jul 18 2020 17:21
    PatrickSachs opened #100
  • Mar 11 2020 08:32
    heinrich-fresh edited #99
  • Mar 11 2020 08:31
    heinrich-fresh edited #99
  • Mar 11 2020 08:30
    heinrich-fresh closed #99
  • Mar 11 2020 08:30
    heinrich-fresh opened #99
  • May 31 2019 19:29
    decasm closed #7
  • May 31 2019 17:51
    decasm closed #98
  • May 31 2019 17:51
    decasm closed #8
  • May 31 2019 17:42
  • May 31 2019 17:39
  • May 31 2019 17:37
    decasm opened #98
  • May 31 2019 17:37
    decasm opened #7
  • May 31 2019 17:37
    decasm opened #8
Anne-Gwenn Kettunen
@Annwenn
:)
thanks
Shane Logsdon
@slogsdon
np!
@Annwenn @YellowApple would you two like push privileges for the hex packages?
Anne-Gwenn Kettunen
@Annwenn
oh my… what a promotion :O
@slogsdon I'd be honoured.
Shane Logsdon
@slogsdon
haha i figured it would be better if it wasn't just me. pm me your email used for your hex account, and i'll add you
Anne-Gwenn Kettunen
@Annwenn
Well now this is embarrassing because I don't own the address anymore :D
I'm going to register a new user…
Shane Logsdon
@slogsdon
whoops! i've been there. no worries
Anne-Gwenn Kettunen
@Annwenn
(well, hopefully I just have one package.)
=)
Ryan S. Northrup (RyNo)
@YellowApple
@slogsdon Sure.
Anne-Gwenn Kettunen
@Annwenn
@slogsdon and @YellowApple if you have a moment to take a look at #83
I really feel like I'm missing something…
Ryan S. Northrup (RyNo)
@YellowApple
Have you tried an absolute instead of relative path when creating the stylesheet link (i.e. /css/foo.css instead of css/foo.css)? In the midst of Thanksgiving rituals, so can't dive in further at the moment, but I suspect it's some Sugar quirk with path relativity.
Anne-Gwenn Kettunen
@Annwenn
@YellowApple Thanks :) it works now.
Ryan S. Northrup (RyNo)
@YellowApple
Wewt
Victor Justo V.
@vjustov
jevy
oops, that wasnt suppose to go here
Ryan S. Northrup (RyNo)
@YellowApple
Hey @slogsdon, can you verify that I still have Hex push privileges for Sugar? mix hex.publish is whining with account not authorized for this action.
(Or if you could just do the push, that'd be fine, too).
Shane Logsdon
@slogsdon
@YellowApple for some reason you didn't. i've added you as an owner once more and published 0.4.11 + docs
Ryan S. Northrup (RyNo)
@YellowApple
Beautiful, thanks
K.I. (Dennis) Jung
@djKooks
Just find here...nice to join~
Devon Smith
@decasm
Hi. I've started using sugar for a project but I'm looking to make updates so that development is smoother and I can release in distilery. Looking to coordinate my work.
Ryan S. Northrup (RyNo)
@YellowApple
Sorry for the late response! Any help with making Sugar Distillery-friendly would surely be welcome.
Elixir 1.9 also introduced its own release mechanism, which I'm in the process of wrapping my head around for my New Year's Resolution of "get Sugar in shape and in-line with current Elixir". I strongly suspect Distillery will end up rebasing some or all of its functionality on top of Elixir releases, so that's where I'm inclined to focus my efforts.
Devon Smith
@decasm
Thanks for getting back to me. A lot of the changes I made early on were simply to eliminate warnings and errors the compiler was spitting out. But when I started to try to build and run a distillery release, I ran into a lot of trouble with the Mix calls in the running app. At that point, I started making more signicant changes to refactor or replace that code - to remove any :prod runtime dependency on Mix. I thought about writing some macros that would compile different code for :dev and :prod, maybe :test, but I'm still new to Elixir and wanted to see if you had better ideas.
FYI, I'm going to be unavailable all next week, so no rush getting back to me.
Ryan S. Northrup (RyNo)
@YellowApple
Yeah, I'd say putting together a list of those calls and figuring out if they really need to be in Sugar itself (v. some :dev-only and/or optional dependency thereof) would be a good start, and would probably be cleaner than trying to do this through macros.
(For example: splitting off the Mix tasks into a separate :sugar_tasks package or something, then adding {:sugar_tasks, "~> 0.5", only: [:dev]} or something along those lines to Sugar's mix.exs)
Devon Smith
@decasm
The one that required the most reworking was the access to eex templates when in :prod. Parts of that code (in Finder and Controller/Helpers, I think) were regularly looking at the filesystem to try and recompile and reload the templates. But yeah, I'll put together a list of them and get back to you.
Ryan S. Northrup (RyNo)
@YellowApple
Yeah, I know the template system has been on our TODO list to refactor and clean up for awhile now. Lots of room for simplification there.
Devon Smith
@decasm
Wrote up a few issues I was having. It's not comprehensive yet, but I figured I'd move things forward. https://gist.github.com/decasm/64d4f9734d0ad1de94d62316f3924655