[15/01/2014] Upstream Maintenance (16th to 17th)

Moved NodeBB Development
  • From our upstream hosting provider:

    START: 2014-01-16 20:00 PST (UTC-8 )
    END: 2014-01-17 04:00 PST (UTC-8 )

    We will update and expand our network infrastructure to provide additional capacity and expansion of the SFO1 datacenter.

    Expected Impact:

    There will be several minutes of packet loss and high latency as we upgrade our peering and core routers. We will take our peering links out of service one at a time and then transition the rest of
    the network over to the new hardware.

    Resolution:

    Due to the popularity of this datacenter, it has grown to the size that our networking infrastructure cannot support more droplets or future features including IPv6. This upgrade will bring the datacenter
    into our high capacity design and enable it for IPv6.

    This preventative maintenance should not affect NodeBBs hosted on sf-1.

  • julianJ julian moved this topic from Announcements on

Suggested Topics


  • 0 Votes
    9 Posts
    3k Views

    https://www.nodebb.se/topic/7/installation-av-nodebb-anteckningar

    That is how i Do it 😉 I guess you can figure it out even if its in Swedish 😛

  • 0 Votes
    2 Posts
    910 Views

    Why would you do this? You should never be storing the password in more than one database.

    I think you seriously need to re-think the design of your app.

    If you want to retrieve the hashed password. You need to call the database directly.

    db.getObjectField('user:' + confirmObj.uid, 'password', function (err, password) { // Now you have the hashed password. })
  • 0 Votes
    4 Posts
    2k Views

    Anyone knows if theres the possibility of registering an user link in the dropdown, that will be public only? Like the case for example of the "chat link", but registered vía filter:user.profileLinks hook.

    Since in that hook theres no user info, i cannot check if the user visualizing the page is the users itself that is visualizing his/her profile or if the user its logged in, to restrict the link registration.

    I want to implement the functionality of "ignore users" showing a link that can be used to ignore, unignore from the user profile. But it has no sense to show the link "ignore/unignore user" if it is the user itself or the user visiting the profile is not logged in.

    I know it can be easilly achived by adding one more attribute to the link object and modifying the menu.tpl with minor changes to reflect this behaviour (checking the new field), and without altering the existing behaviour of the theme. If the answer to the previous question is "no", what is needed to get a pull request including this behaviour accepted? Modification in all stable themes? (persona,lavender,vanilla?).
    Or would it be more suitable a request of a new action hook for action:user:viewProfile for example? To be able to make business logic checks with the data, and altering the content sent to the page for example?

    PS: Is there any way of contributing to document the list of hooks with a short explanation of each one? For example when they're fired and wich information do they send? I think it would be a good improvement for the documentation in order to make it easy to the plugin dev to without the need to dive into the core and check each hook one by one looking for one satisfying their needs. I wouldn't mind to throw 2/3 lines explaining the hooks I found useful that i'm seeing on my little plugin experiments from a noob perspective. Ping @administrators

    Thanks again and sorry for modifying the thread question.

  • 0 Votes
    6 Posts
    3k Views

    Disney is notoriously litigious, in addition to a slew of other questionable elements.

  • 0 Votes
    4 Posts
    1k Views

    i swear these were randomly generated in my head.