Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Release Bell
  3. [Feature Request] Email Updates

[Feature Request] Email Updates

Scheduled Pinned Locked Moved Solved Release Bell
16 Posts 4 Posters 2.5k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      T Offline
      thetomester13
      App Dev
      wrote on last edited by
      #1

      I had some thoughts about updates for the emails that ReleaseBell sends out.

      1. The emails themselves can be mobile friendly. Right now if I open an email on my phone it's zoomed all the way out and I can't make out what it's saying without zooming in. I believe this should be pretty straight forward.
      2. Can each email include the blurb from the release? This would make it so that you don't have to leave your email client to see what the updates actually were (at least in cases where the repo owner added a blurb to the release at all).

      Finally, I volunteer to contribute these updates if it's interesting at all and welcome?

      girishG 2 Replies Last reply
      3
      • T thetomester13

        I had some thoughts about updates for the emails that ReleaseBell sends out.

        1. The emails themselves can be mobile friendly. Right now if I open an email on my phone it's zoomed all the way out and I can't make out what it's saying without zooming in. I believe this should be pretty straight forward.
        2. Can each email include the blurb from the release? This would make it so that you don't have to leave your email client to see what the updates actually were (at least in cases where the repo owner added a blurb to the release at all).

        Finally, I volunteer to contribute these updates if it's interesting at all and welcome?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @thetomester13 Both sound great to me! Let us know if you need any help.

        T 1 Reply Last reply
        2
        • girishG girish

          @thetomester13 Both sound great to me! Let us know if you need any help.

          T Offline
          T Offline
          thetomester13
          App Dev
          wrote on last edited by
          #3

          @girish this took longer than expected, but here is the Merge Request. Happy to get your notes on it and make adjustments where needed. Turns out getting the Release Body for both Github and Gitlab was challenging since their API's do not line up 1-to-1. Hopefully this is a decent solution around that.

          girishG 1 Reply Last reply
          2
          • T thetomester13

            @girish this took longer than expected, but here is the Merge Request. Happy to get your notes on it and make adjustments where needed. Turns out getting the Release Body for both Github and Gitlab was challenging since their API's do not line up 1-to-1. Hopefully this is a decent solution around that.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            @thetomester13 thanks! I merged it. It seems that highlight.js which comes from helper-markdown is deprecated. I see this when installing (there's upstream issues https://github.com/helpers/helper-markdown/issues/15 and https://github.com/helpers/helper-markdown/issues/14 about this):

            > highlight.js@9.18.5 postinstall /home/girish/yellowtent/releasebell/node_modules/highlight.js
            > node deprecated.js
            
            -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
            
              Verion 9 of Highlight.js has reached EOL.  It will no longer
              be supported or receive security updates in the future.
              Please upgrade to version 10 or encourage your indirect
              dependencies to do so.
            
              For more info:
              
              https://github.com/highlightjs/highlight.js/issues/2877
              https://github.com/highlightjs/highlight.js/blob/master/VERSION_10_UPGRADE.md
             
            -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
            
            1 Reply Last reply
            0
            • T thetomester13

              I had some thoughts about updates for the emails that ReleaseBell sends out.

              1. The emails themselves can be mobile friendly. Right now if I open an email on my phone it's zoomed all the way out and I can't make out what it's saying without zooming in. I believe this should be pretty straight forward.
              2. Can each email include the blurb from the release? This would make it so that you don't have to leave your email client to see what the updates actually were (at least in cases where the repo owner added a blurb to the release at all).

              Finally, I volunteer to contribute these updates if it's interesting at all and welcome?

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by girish
              #5

              @thetomester13 Given that it's really just one file - https://github.com/helpers/helper-markdown/blob/master/index.js, do you think we can just remove usage of that module entirely? Just put that file in releasebell itself (or make a function) and bump the deps?

              T 1 Reply Last reply
              0
              • girishG girish

                @thetomester13 Given that it's really just one file - https://github.com/helpers/helper-markdown/blob/master/index.js, do you think we can just remove usage of that module entirely? Just put that file in releasebell itself (or make a function) and bump the deps?

                T Offline
                T Offline
                thetomester13
                App Dev
                wrote on last edited by
                #6

                @girish yikes, totally missed the fact that helpers/helper-markdown is not really supported anymore, quite unfortunate as it seems the author just stopped responding 😕

                do you think we can just ... put that file in releasebell itself (or make a function) and bump the deps?

                Anyway, yes, I think this is a fine way to move forward. Unfortunately, the now-deprecated module was the best solution I found to render Markdown in handlebars. And as you mentioned, since it's quite straight forward, pulling it into ReleaseBell probably wouldn't be a big deal. Even more so, I don't believe we use the hightlight method defined on line 40, so we shouldn't even need to bring in the highlight.js package.

                nebulonN 1 Reply Last reply
                1
                • T thetomester13

                  @girish yikes, totally missed the fact that helpers/helper-markdown is not really supported anymore, quite unfortunate as it seems the author just stopped responding 😕

                  do you think we can just ... put that file in releasebell itself (or make a function) and bump the deps?

                  Anyway, yes, I think this is a fine way to move forward. Unfortunately, the now-deprecated module was the best solution I found to render Markdown in handlebars. And as you mentioned, since it's quite straight forward, pulling it into ReleaseBell probably wouldn't be a big deal. Even more so, I don't believe we use the hightlight method defined on line 40, so we shouldn't even need to bring in the highlight.js package.

                  nebulonN Away
                  nebulonN Away
                  nebulon
                  Staff
                  wrote on last edited by
                  #7

                  @thetomester13 I guess in the long run we can move this to markdown-it which seems to be properly supported

                  T 1 Reply Last reply
                  0
                  • nebulonN nebulon

                    @thetomester13 I guess in the long run we can move this to markdown-it which seems to be properly supported

                    T Offline
                    T Offline
                    thetomester13
                    App Dev
                    wrote on last edited by
                    #8

                    @nebulon that's a great point! I was always looking at how to integrate Markdown rendering with the Handlebars templating, but we could simply try to get Markdown as HTML and then pass it into the email template.

                    nebulonN 1 Reply Last reply
                    0
                    • T thetomester13

                      @nebulon that's a great point! I was always looking at how to integrate Markdown rendering with the Handlebars templating, but we could simply try to get Markdown as HTML and then pass it into the email template.

                      nebulonN Away
                      nebulonN Away
                      nebulon
                      Staff
                      wrote on last edited by
                      #9

                      @thetomester13 we are running the new version currently for testing still and it is a huge improvement. Thanks @thetomester13 totally worth it 🙂

                      1 Reply Last reply
                      1
                      • girishG Offline
                        girishG Offline
                        girish
                        Staff
                        wrote on last edited by
                        #10

                        Indeed, it's pretty great. In fact, just one day in, I don't know how I lived without this for so long 🙂

                        (on a side note, there was a crash which I have fixed).

                        T robiR 2 Replies Last reply
                        1
                        • girishG girish

                          Indeed, it's pretty great. In fact, just one day in, I don't know how I lived without this for so long 🙂

                          (on a side note, there was a crash which I have fixed).

                          T Offline
                          T Offline
                          thetomester13
                          App Dev
                          wrote on last edited by
                          #11

                          🙃 that makes me happy to hear! Glad I can contribute!

                          @girish curious, what was causing the crash?

                          1 Reply Last reply
                          0
                          • girishG girish

                            Indeed, it's pretty great. In fact, just one day in, I don't know how I lived without this for so long 🙂

                            (on a side note, there was a crash which I have fixed).

                            robiR Offline
                            robiR Offline
                            robi
                            wrote on last edited by
                            #12

                            @girish said in [Feature Request] Email Updates:

                            Indeed, it's pretty great. In fact, just one day in, I don't know how I lived without this for so long

                            What's the workflow that so much better?

                            Conscious tech

                            girishG 1 Reply Last reply
                            0
                            • robiR robi

                              @girish said in [Feature Request] Email Updates:

                              Indeed, it's pretty great. In fact, just one day in, I don't know how I lived without this for so long

                              What's the workflow that so much better?

                              girishG Offline
                              girishG Offline
                              girish
                              Staff
                              wrote on last edited by
                              #13

                              @robi the release information is now straight in the new release notitfication email. Previously, one had to click through and visit via the browser etc.

                              06b2708c-cdd0-4953-b100-b96c805a3f86-image.png

                              T 1 Reply Last reply
                              3
                              • girishG girish

                                @robi the release information is now straight in the new release notitfication email. Previously, one had to click through and visit via the browser etc.

                                06b2708c-cdd0-4953-b100-b96c805a3f86-image.png

                                T Offline
                                T Offline
                                thetomester13
                                App Dev
                                wrote on last edited by
                                #14

                                @girish @nebulon any idea when the new version will be pushed out? I'm still on the official Cloudron Store version, so don't have these updates yet.

                                nebulonN 1 Reply Last reply
                                0
                                • T thetomester13

                                  @girish @nebulon any idea when the new version will be pushed out? I'm still on the official Cloudron Store version, so don't have these updates yet.

                                  nebulonN Away
                                  nebulonN Away
                                  nebulon
                                  Staff
                                  wrote on last edited by
                                  #15

                                  @thetomester13 ah yes, sorry forgot about this. We are using it already for some time now and initial issues were fixed, so no reason not to update it. Will go ahead now.

                                  nebulonN 1 Reply Last reply
                                  1
                                  • nebulonN nebulon

                                    @thetomester13 ah yes, sorry forgot about this. We are using it already for some time now and initial issues were fixed, so no reason not to update it. Will go ahead now.

                                    nebulonN Away
                                    nebulonN Away
                                    nebulon
                                    Staff
                                    wrote on last edited by
                                    #16

                                    Updated now

                                    1 Reply Last reply
                                    4
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                      • Login

                                      • Don't have an account? Register

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Bookmarks
                                      • Search