social.sokoll.com

Search

Items tagged with: ruby

After many years of packaging work by many contributors, yesterday I was able to install #diaspora native debian package.

Out of 101 direct dependencies and 223 total dependencies (if you consider build dependencies for JavaScript assets like grunt, gulp, rollup, webpack, babel etc, the actual number required to build everything from source is much larger - in Debian, we build every package in main section from source), only 8 of them needed to be handled outside of debian packages.
  • autprefixer-rails gem had to be installed from rubygems.org because debian does not have browserify packaged and building with rollup and webpack created a broken bundle.
  • active_model_serializers had to be installed from rubygems.org because debian had a newer incompatible version.
  • 6 gems had to be vendored because diaspora is still using sass-rails which is dead upstream and debian already moved to sassc-rails.
  • I still need to integrate systemd unit files to handle starting and stopping of the services automatically.
  • There is also issues in ui, possibly because of broken builds in front end javascript libraries. I can see errors in the browser web console.
If you'd like to help test it, follow https://wiki.debian.org/Diaspora#Buster_Fasttrack.2Fpersonal_repo

If any of you are good in #nodejs #javascript or #ruby #rails, I'd appreciate some help to fix these remaining issues.

If you are good in #devops #sysadmin you can help test the package or help with running diaspora in production (we also have a diaspora-installer package that installs all dependencies from rubygems.org. We are running this package in production for many years at https://poddery.com and https://diasp.in).

Thanks to everyone who contributed to this effort over many years.

#debian-diaspora #debian #debian-packaging #packaging
 
After many years of packaging work by many contributors, yesterday I was able to install #diaspora native debian package.

Out of 101 direct dependencies and 223 total dependencies (if you consider build dependencies for JavaScript assets like grunt, gulp, rollup, webpack, babel etc, the actual number required to build everything from source is much larger - in Debian, we build every package in main section from source), only 8 of them needed to be handled outside of debian packages.
  • autprefixer-rails gem had to be installed from rubygems.org because debian does not have browserify packaged and building with rollup and webpack created a broken bundle.
  • active_model_serializers had to be installed from rubygems.org because debian had a newer incompatible version.
  • 6 gems had to be vendored because diaspora is still using sass-rails which is dead upstream and debian already moved to sassc-rails.
  • I still need to integrate systemd unit files to handle starting and stopping of the services automatically.
  • There is also issues in ui, possibly because of broken builds in front end javascript libraries. I can see errors in the browser web console.
If you'd like to help test it, follow https://wiki.debian.org/Diaspora#Buster_Fasttrack.2Fpersonal_repo

If any of you are good in #nodejs #javascript or #ruby #rails, I'd appreciate some help to fix these remaining issues.

If you are good in #devops #sysadmin you can help test the package or help with running diaspora in production (we also have a diaspora-installer package that installs all dependencies from rubygems.org. We are running this package in production for many years at https://poddery.com and https://diasp.in).

Thanks to everyone who contributed to this effort over many years.

#debian-diaspora #debian #debian-packaging #packaging
 
Hallo zusammen, ich bin #neuhier. Ich interessiere mich für #aquaristik, #elektronik, #holzbearbeitung, #leipzig und #ruby. Danke für die Einladung, Felix!
 
Hallo zusammen, ich bin #neuhier. Ich interessiere mich für #aquaristik, #elektronik, #holzbearbeitung, #leipzig und #ruby. Danke für die Einladung, Felix!
 
We hired one in our #Alameda office but are looking for another in either our #Minneapolis #Minnesota office or the #California office

Nice-to-haves*:
Knowledge of C/C++ and #Java and experience with #PHP/MySQL
Knowledge of Unix & #Linux (we previously supported #BSD, #Solaris, and perhaps some others, but just Linux now)
Basic networking experience
Experience with Perforce, #Git, or other version control software is desirable
Bachelor’s Degree in Computer Science or similar or relevant work experience
2 or more years’ experience providing technical support directly to enterprise customers

These are listed as requirements on the site, but they make zero since to me. There is literally no one on the Minneapolis team that knows C/C++. We do have a C/C++ API, so yes, it would be good if you knew that, but most people use our derived APIs (#Perl, #Python, .NET, #Ruby, #PHP, and maybe that is it). Java, like #C, is a native API.
Also, we do support #Windows and #Mac, so unclear why knowledge of that is not listed.

Experience in customer support or customer-facing role
Strong analytics and problem-solving skills
Strong debugging skills
Ability to work in a team environment and contribute ideas and improvements
Able to work well under pressure and prioritize accordingly
Responsibilities:
Represent Perforce as the first point of contact for customer’s technical requests.
Review and research customer issues to determine and provide the best resolution.
Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
Resolve database and performance issues.
Research, document, and escalate cases according to procedure.
Provide customer driven feedback to functional areas in order to influence process/product improvements.
Author technical documents on common issues and solutions in order to build the knowledge base.
Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
Create and set up test environments to reproduce and resolve customer issues.
Recreate customer environments to reproduce issues and experiment with possible solutions.
 
We hired one in our #Alameda office but are looking for another in either our #Minneapolis #Minnesota office or the #California office

Nice-to-haves*:
Knowledge of C/C++ and #Java and experience with #PHP/MySQL
Knowledge of Unix & #Linux (we previously supported #BSD, #Solaris, and perhaps some others, but just Linux now)
Basic networking experience
Experience with Perforce, #Git, or other version control software is desirable
Bachelor’s Degree in Computer Science or similar or relevant work experience
2 or more years’ experience providing technical support directly to enterprise customers

These are listed as requirements on the site, but they make zero since to me. There is literally no one on the Minneapolis team that knows C/C++. We do have a C/C++ API, so yes, it would be good if you knew that, but most people use our derived APIs (#Perl, #Python, .NET, #Ruby, #PHP, and maybe that is it). Java, like #C, is a native API.
Also, we do support #Windows and #Mac, so unclear why knowledge of that is not listed.

Experience in customer support or customer-facing role
Strong analytics and problem-solving skills
Strong debugging skills
Ability to work in a team environment and contribute ideas and improvements
Able to work well under pressure and prioritize accordingly
Responsibilities:
Represent Perforce as the first point of contact for customer’s technical requests.
Review and research customer issues to determine and provide the best resolution.
Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
Resolve database and performance issues.
Research, document, and escalate cases according to procedure.
Provide customer driven feedback to functional areas in order to influence process/product improvements.
Author technical documents on common issues and solutions in order to build the knowledge base.
Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
Create and set up test environments to reproduce and resolve customer issues.
Recreate customer environments to reproduce issues and experiment with possible solutions.
 
Ich hatte es vergessen und poste es hier, damit ich es nicht wieder vergesse, aber auch für euch und alle, die es noch nicht wissen. Eine gute

#Alternative für #Instagram


is #Pixelfed.
Instanzen z.B. unter https://pixelfed.de/ oder https://pixelfed.social/
Infos unter https://pixelfed.org/ und https://fediverse.network/pixelfed

#Diaspora würde theoretisch auch als #Instagram-Alternative herhalten können, aber da man beim Hochladen von #Fotos nichtmal die Reihenfolge der #Bilder festlegen kann. leider doch nicht. Das wäre die Minimalvoraussetzung, wie ich im Gespräch mit einigen #Fotografen herausgefunden habe, vielleicht erbarmt sich ja einer unserer Entwicklerinnen.

#Insta #Ruby
 
Ich hatte es vergessen und poste es hier, damit ich es nicht wieder vergesse, aber auch für euch und alle, die es noch nicht wissen. Eine gute

#Alternative für #Instagram


is #Pixelfed.
Instanzen z.B. unter https://pixelfed.de/ oder https://pixelfed.social/
Infos unter https://pixelfed.org/ und https://fediverse.network/pixelfed

#Diaspora würde theoretisch auch als #Instagram-Alternative herhalten können, aber da man beim Hochladen von #Fotos nichtmal die Reihenfolge der #Bilder festlegen kann. leider doch nicht. Das wäre die Minimalvoraussetzung, wie ich im Gespräch mit einigen #Fotografen herausgefunden habe, vielleicht erbarmt sich ja einer unserer Entwicklerinnen.

#Insta #Ruby
 
Later posts Earlier posts