There’s plenty of articles out there explaining what the changes are (https://blog.chromium.org/2020/02/samesite-cookie-changes-in-february.html), why they’ve been done (https://www.troyhunt.com/promiscuous-cookies-and-their-impending-death-via-the-samesite-policy) and how to ‘theoretically’ fix them with simple code examples, but we haven’t stumbled upon many articles explaining ‘practical’ solutions to apply to a Drupal site to actually fix the issues that arise due to the stricter cookie policies implemented since the Chrome 80 release.
It allows to very easily create engaging learning paths, assess the knowledge of students, employees or partners, and monitor their achievements thanks to the reporting dashboards. It offers innovative features like adaptive learning depending on the user’s results, automatic skill management, a mobile application, and much more…
- manage training paths organized in courses, modules, and activities
- configure adaptive learning paths
- manage and ensure skill acquisition by students
- assess students thanks to varied quizzes
- manage blended learning by combining online modules with in-house sessions and virtual classrooms
- award certificates to successful students
- sell your trainings online
- facilitate interactions thanks to live meetings, forums and chats
- and much more!
Opigno LMS is fully compliant with SCORM (1.2 and 2004 v3) and Tin Can (xAPI).
It integrates the innovative H5P technology, making possible to create rich interactive training contents.
Source: Opigno LMS
What a Drupal website for distance learning should be like? We will talk about technologies for students’ assignments, collecting statistics on the work done, functionality, Drupal modules, and distributions for its work.
Source: Drupal for e-Learning websites
Knowledge management is a key to success in modern enterprises—but it is not exactly easy to achieve. Keeping track of all relevant details across all employees is a huge challenge, especially in agile environments, which most companies say they are.
Most companies resort to buying wiki-like solutions, such as Confluence from Atlassian, which exposes them to the lock-in effect of proprietary software. But many would do well to consider BlueSpice, an open source alternative to Atlassian Confluence that has a noble ancestry: it’s based on Wikipedia’s MediaWiki.
Drupal 8 content migrations from CSV or spreadsheet, full tutorial. Learn to import complex data from CSV in 20 minutes, example code included.
Time to start thinking about this.
Any time you have a VPC, you’ll likely need some way to gain access to the resources within the VPC from your local box. Typically, the way to do that is to run a bastion (or jumpbox) which you and your team can SSH into. The downside is that you are exposing an entry point into your network that is accessible by multiple people and running 24×7. And depending on how you manage permissions, you may not be able to restrict access to the box via IAM. Obviously, this is not ideal.
Luckily, we have Fargate.
With Fargate, we no longer need to maintain permanent bastion instances—we can create bastions when needed and tear them down when no longer in use. We can lock down bastion instances to an individual user both in terms of SSH keys and IP address. And we can restrict access via IAM to both the API used to manage bastions and to which SSH keys are used to log into an instance.
All in all, we save on infrastructure spend while reducing our attack surface.
This looks like an intriguing solution to a problem that has bothered me for years. Running sshd provides an attack surface for bad actors just because it’s there. Ideally you should never expose the ssh port to the public network, even if it is well secured. Bastion hosts are a well known solution to this but one that is often not implemented for one reason or another. Turning it inot a service seems like a good idea.
Vitess | A database clustering system for horizontal scaling of MySQL https://vitess.io/
Citing ‘zero lethal threat’ to students, Purdue works to reopen college for fall 2020 https://www.usatoday.com/story/news/education/2020/04/25/coronavirus-college-fall-2020-purdue-university-mitch-daniels/3018469001/
Continuous Integration (CI) workflows are considered a best practice these days. As in, you work with your version control system (Git), and as you do, CI is doing work for you like running tests, sending notifications, and deploying code. That last part is called Continuous Deployment (CD). But shipping code to a production server often requires paid services. With GitHub Actions, Continuous Deployment is free for everyone. Let’s explore how to set that up.
Every day, we do about 12 scheduled deploys. During each deploy, an engineer is designated as the deploy commander in charge of rolling out the new build to production. This is a multistep process that ensures builds are rolled out slowly so that we can detect errors before they affect everyone. These builds can be rolled back if there is a spike in errors and easily hotfixed if we detect a problem after release.
Deploys at Slack https://slack.engineering/deploys-at-slack-cd0d28c61701
This is an interesting look at how development is done at Slack. Weirdly, I’m pretty sure I couldn’t get away with this sort of iteration anymore because our community it’s relatively small and hesitant to change.
Once upon a time I did make changes on the fly to add new features or tweak the interface but now folks depends on us to maintain a certain level of stability as they learn about it teach the law. Of course it could be that as I get older I’m less tolerant of getting pinged about changes