Actualizaciones recientes Mostrar/Ocultar Comentarios | Atajos de teclado

  • manuelmc 4:17 pm el 11 July, 2021 Enlace permanente | Respuesta
    Etiquetas: macOS   

    Messing with FileVault 

    I know I have your attention. Well, I’ve been doing just that, because I’m using macOS Catalina in my old (but working!) MacBook Aluminum Unibody.

    This is not a supported configuration, so I’m not on the safe side here…

    (Más …)
  • manuelmc 8:27 pm el 7 March, 2021 Enlace permanente | Respuesta
    Etiquetas: backup, cloud, unix   

    ownCloud backup and rclone 

    Having a [virtual|cloud] drive in which I could keep some common tools, old works’ backup, unfrequently used ISO images and things like that, is an issue that has been coming to my mind for so long.

    As I was thinking in the order of hundreds of gigabytes, Dropbox was no longer an option for me. I decided to go for ownCloud. First I tried OwnCube, which I have to say it’s a great hosted option. However, as I have already a server in which I can host it myself, I went that direction and tried to learn something in the process.

    (Más …)
  • manuelmc 12:19 am el 18 February, 2021 Enlace permanente | Respuesta
    Etiquetas: gmail, wordpress   

    Sending email from within WordPress 

    In my recent this-thing-is-not-working spree, I’ve fortunately found WP Mail SMTP. The thing that made me happy the most is that it works.

    Weird mascot logo
    (Más …)
  • manuelmc 11:09 pm el 10 February, 2021 Enlace permanente | Respuesta  

    Homebrew and SSL certificates 

    There’s an issue with some packages in Homebrew regarding SSL certificates. Once in a while I need to remember which env variable do I have to set in order to install its upgrades with Homebrew. LibreOffice is one of them.

    This is the answer in Stack Overflow:

    echo insecure >> ~/.curlrc
    brew install --cask libreoffice

    This way we’ll force Homebrew to read our preferences whenever it runs curl .

    • Ruso 9:23 am el 15 febrero, 2021 Enlace permanente | Respuesta

      I think it’s not a good idea to use options that allow the use of insecure certificates, especially if it’s to install software.

      Certificates are used to ensure the authenticity of the site from which you are downloading the software.

      There are other ways to verify that the software you are going to install is legitimate, but they must be supported by the package manager.

      • manuelmc 9:28 am el 15 febrero, 2021 Enlace permanente | Respuesta

        Well, in those cases I make sure the origin of the software is the one I wanted it to be. The issue at hand is that cURL is not able to handle the whole certificate chain in a certain case, but the certificate is valid. If you go and download that LibreOffice link with a web browser, it works.

        • Ruso 9:40 am el 15 febrero, 2021 Enlace permanente | Respuesta

          If you put insecure option into the curlrc file, this change is permanent. Curl accepts all insecure certificates.

          I think it’s necessary to remove this option after using it in this special case.

          • manuelmc 12:21 pm el 7 marzo, 2021 Enlace permanente | Respuesta

            Well, what it happens is that `brew` forces you to do this way, as it uses cURL without accepting command line modifiers. For sure, whenever you’re not using it, you’d better have .curlrc without tha option.

  • manuelmc 10:17 pm el 7 February, 2021 Enlace permanente | Respuesta
    Etiquetas: bigdata   

    The age of Surveillance Capitalism 

    Browsing through YouTube, I came across this interesting Dutch documentary from VPRO channel about information, power, social networks and the implications of any combination of them.

    De Grote Dataroof
    (Más …)
  • manuelmc 7:14 am el 18 July, 2017 Enlace permanente | Respuesta  

    Microsoft eBook giveaway 

    During my current interest about Azure cloud services, I’ve spotted this link with tons of free available ebooks about some interesting subjects.

  • manuelmc 12:44 pm el 26 February, 2017 Enlace permanente | Respuesta  

    A Gitlab disaster: What we can learn. 

    After the well known Gitlab disaster / outage / disclosure, that could have been followed even in a live stream, some people think that they can extract certain conclusions.

    The way they handled the incident can be seen a bit blurry or inadequate, to say the least. Anyway, nobody can say they’re not transparent.

    Anyway, following this incident and the sea of news that came after, somebody kindly gave me this link with some interesting knowledge:

    Gitlab Team Handbook

  • manuelmc 5:33 pm el 20 March, 2016 Enlace permanente | Respuesta  

    Good teamwork = being nice. 

    I’ve been reading part of this article and I totally agree with what I’ve read.

    After years of intensive analysis, Google discovers the key to good teamwork is being nice

    I really think that there’s no special treatment or benefit you can grant to your team / coworkers / employees that guarantee success.
    BUT, if you really listen, if you really behave with them, and take their suggestions and ideas into account, it will be enough.

Crea una nueva entrada
Siguiente entrada / Siguiente comentario
anterior entrada/anterior comentario
mostrar/ocultar comentarios
ir al encabezado
ir a iniciar sesión
mostrar/ocultar ayuda
shift + esc