Anthos Security: modernize your security posture for cloud native applicationsGreg Castle
In this talk we describe a high-level workflow for securing Kubernetes clusters across GKE, Anthos on AWS, and Anthos On-Prem. There's a lot to cover: about 30 products and features across 3 platforms!
Fantastic Buildpacks and Where to Find ThemJoe Kutner
Adventure awaits you as we journey through the buildpack ecosystem. We’ll discuss how to find buildpacks in the wild and examine their different habitats, including Google, Heroku, and Cloud Foundry. In this talk, you’ll learn how to run buildpacks and where to find production ready buildpacks that are perfect for your app.
Introduction to Persistent Identifiers| www.eudat.eu | EUDAT
| www.eudat.eu | What are persistent identifiers? Why use persistent identifiers? Different persistent identifier systems; The HANDLE system; EPIC PID system; Policies; Use cases
Ver 2 July 2017
Anthos Security: modernize your security posture for cloud native applicationsGreg Castle
In this talk we describe a high-level workflow for securing Kubernetes clusters across GKE, Anthos on AWS, and Anthos On-Prem. There's a lot to cover: about 30 products and features across 3 platforms!
Fantastic Buildpacks and Where to Find ThemJoe Kutner
Adventure awaits you as we journey through the buildpack ecosystem. We’ll discuss how to find buildpacks in the wild and examine their different habitats, including Google, Heroku, and Cloud Foundry. In this talk, you’ll learn how to run buildpacks and where to find production ready buildpacks that are perfect for your app.
Introduction to Persistent Identifiers| www.eudat.eu | EUDAT
| www.eudat.eu | What are persistent identifiers? Why use persistent identifiers? Different persistent identifier systems; The HANDLE system; EPIC PID system; Policies; Use cases
Ver 2 July 2017
This slide describe what is the KIND and how to set up the KIND(Kubernetes IN Docker) to have a simple and quickly environment for k8s testing, is also address few issues what KIND fix to make the KIND work, like the certificate issue and DNS issue
A Gentle Introduction To Docker And All Things ContainersJérôme Petazzoni
Docker is a runtime for Linux Containers. It enables "separation of concern" between devs and ops, and solves the "matrix from hell" of software deployment. This presentation explains it all! It also explains the role of the storage backend and compares the various backends available. It gives multiple recipes to build Docker images, including integration with configuration management software like Chef, Puppet, Salt, Ansible. If you already watched other Docker presentations, this is an actualized version (as of mid-November 2013) of the thing!
A brief history of Blinkist backend time. I gave this talk at the Adidas Developer conference in Erlangen. The Adidas developer community is awesome! Go check out their Github repositories for all the project they've contributed https://github.com/adidas
Using Docker multi-stage build to created advanced build pipelines.
With single Dockerfile create lean Docker images for Go, Node, Java and other platforms.
Difference between .net core and .net frameworkAnsi Bytecode
We are all familiar with .NET Core, .NET Framework and how they have been leading the programming world for building mobile, web-based and desktop applications. But wait, are they both same or have different infrastructure? You might be confused about both of them and probably that’s why you’re here.
A presentation delivered to the Melbourne AWS Meetup on the May 24, 2018 . Discusses the implementation of the new AWS Containers sub-generator, which allows JHipster applications to be deployed on Amazon ECS, leveraging Fargate.
The Mono-repo – a contradiction with MicroservicesEficode
Johannes Brüderl
Lead Software Engineer – E.ON SE
Johannes is a Software Engineer for life. He enjoys working on distributed systems and open source products. His preferred tech-stack at this time includes Kubernetes, Apache Kafka and Go. Currently he is working in the IoT Area and leads the development of E.ON’s global IoT Platform to serve E.ON’s products. He is also an active open source contributor and enjoys fixing bugs & writing enhancements for upstream open source projects.
Watch the recording here: https://youtu.be/0KmqEp4VxSQ
Welcome Helm users! CNCF Flux has a best-in-class way to use Helm according to GitOps principles. For you, that means improved security, reliability, and velocity - no more being on the pager on the weekends or having painful troubleshooting or rollback when things go wrong. Built on Kubernetes controller-runtime, Flux’s Helm Controller is an example of a mature software agent that uses Helm’s SDK to full effect.
Flux’s biggest addition to Helm is a structured declaration layer for your releases that automatically gets reconciled to your cluster based on your configured rules:
⭐️ The Helm client commands let you imperatively do things
⭐️ Flux Helm Custom Resources let you declare what you want the Helm SDK to do automatically
During this session, Scott Rigby, Developer Experience Engineer at Weaveworks and Flux & Helm Maintainer, will take you on a tour of Flux’s Helm Controller, share the additional benefits Flux adds to Helm and then walk through a live demo of how to manage helm releases using Flux.
If you want to follow along with Scott’s demo, here are a couple of resources to help you prepare ahead of time:
📄 Flux for Helm Users Docs: https://fluxcd.io/docs/use-cases/helm/
📄 Flux Guide: Manage Helm Releases: https://fluxcd.io/docs/guides/helmreleases/
Speaker Bio:
Scott is a Brooklyn based interdisciplinary artist and Developer Advocate at Weaveworks. He co-founded the Basekamp art and research group in 1998 and the massively collaborative Plausible Artworlds international network. In technology he enjoys helping develop open source software that anyone can use, most recently projects in the cloud native landscape including co-maintaining Helm and Flux. In daily decisions, large or small, he tries to help make the world a better place for everyone.
Windows Server and Docker - The Internals Behind Bringing Docker and Containe...Docker, Inc.
Docker leverages capabilities in Linux like namespaces and cgroups to enable containers and then builds tooling on top to enable users to build distributed apps. A common question is "What about Docker support for Windows?" In this session the Windows engineering leads will dive deep into the primitives within Windows to enable an awesome Docker experience on Windows. This session will also include a live demo of Docker and Windows Server.
.Net framework vs .net core a complete comparisonKaty Slemon
.NET Core Vs. .NET Framework, in this blog post we will provide you interesting and infographics comparison of it so you will choose the right framework.
This slide describe what is the KIND and how to set up the KIND(Kubernetes IN Docker) to have a simple and quickly environment for k8s testing, is also address few issues what KIND fix to make the KIND work, like the certificate issue and DNS issue
A Gentle Introduction To Docker And All Things ContainersJérôme Petazzoni
Docker is a runtime for Linux Containers. It enables "separation of concern" between devs and ops, and solves the "matrix from hell" of software deployment. This presentation explains it all! It also explains the role of the storage backend and compares the various backends available. It gives multiple recipes to build Docker images, including integration with configuration management software like Chef, Puppet, Salt, Ansible. If you already watched other Docker presentations, this is an actualized version (as of mid-November 2013) of the thing!
A brief history of Blinkist backend time. I gave this talk at the Adidas Developer conference in Erlangen. The Adidas developer community is awesome! Go check out their Github repositories for all the project they've contributed https://github.com/adidas
Using Docker multi-stage build to created advanced build pipelines.
With single Dockerfile create lean Docker images for Go, Node, Java and other platforms.
Difference between .net core and .net frameworkAnsi Bytecode
We are all familiar with .NET Core, .NET Framework and how they have been leading the programming world for building mobile, web-based and desktop applications. But wait, are they both same or have different infrastructure? You might be confused about both of them and probably that’s why you’re here.
A presentation delivered to the Melbourne AWS Meetup on the May 24, 2018 . Discusses the implementation of the new AWS Containers sub-generator, which allows JHipster applications to be deployed on Amazon ECS, leveraging Fargate.
The Mono-repo – a contradiction with MicroservicesEficode
Johannes Brüderl
Lead Software Engineer – E.ON SE
Johannes is a Software Engineer for life. He enjoys working on distributed systems and open source products. His preferred tech-stack at this time includes Kubernetes, Apache Kafka and Go. Currently he is working in the IoT Area and leads the development of E.ON’s global IoT Platform to serve E.ON’s products. He is also an active open source contributor and enjoys fixing bugs & writing enhancements for upstream open source projects.
Watch the recording here: https://youtu.be/0KmqEp4VxSQ
Welcome Helm users! CNCF Flux has a best-in-class way to use Helm according to GitOps principles. For you, that means improved security, reliability, and velocity - no more being on the pager on the weekends or having painful troubleshooting or rollback when things go wrong. Built on Kubernetes controller-runtime, Flux’s Helm Controller is an example of a mature software agent that uses Helm’s SDK to full effect.
Flux’s biggest addition to Helm is a structured declaration layer for your releases that automatically gets reconciled to your cluster based on your configured rules:
⭐️ The Helm client commands let you imperatively do things
⭐️ Flux Helm Custom Resources let you declare what you want the Helm SDK to do automatically
During this session, Scott Rigby, Developer Experience Engineer at Weaveworks and Flux & Helm Maintainer, will take you on a tour of Flux’s Helm Controller, share the additional benefits Flux adds to Helm and then walk through a live demo of how to manage helm releases using Flux.
If you want to follow along with Scott’s demo, here are a couple of resources to help you prepare ahead of time:
📄 Flux for Helm Users Docs: https://fluxcd.io/docs/use-cases/helm/
📄 Flux Guide: Manage Helm Releases: https://fluxcd.io/docs/guides/helmreleases/
Speaker Bio:
Scott is a Brooklyn based interdisciplinary artist and Developer Advocate at Weaveworks. He co-founded the Basekamp art and research group in 1998 and the massively collaborative Plausible Artworlds international network. In technology he enjoys helping develop open source software that anyone can use, most recently projects in the cloud native landscape including co-maintaining Helm and Flux. In daily decisions, large or small, he tries to help make the world a better place for everyone.
Windows Server and Docker - The Internals Behind Bringing Docker and Containe...Docker, Inc.
Docker leverages capabilities in Linux like namespaces and cgroups to enable containers and then builds tooling on top to enable users to build distributed apps. A common question is "What about Docker support for Windows?" In this session the Windows engineering leads will dive deep into the primitives within Windows to enable an awesome Docker experience on Windows. This session will also include a live demo of Docker and Windows Server.
.Net framework vs .net core a complete comparisonKaty Slemon
.NET Core Vs. .NET Framework, in this blog post we will provide you interesting and infographics comparison of it so you will choose the right framework.
Presentasi disampaikan dalam kegiatan KPPTI 2023. Aplikasi dikembangkan tim FossStudio : Lead Project : Dwi Fajar Saputra Anggota : Yusac Firmansyah (Core Programmer), Iman Jauhari (Documentation).
Pemanfaatan Open data dan Aplikasi Karya Duraspace di PerpustakaanDwi Fajar Saputra
Materi dibawakan pada kegiatan FPPTI DKI Jakarta, 22-23 Juli 2019 di Kalbis Institute.
Kumpulan materi didapatkan dari beberapa literatur dan hasil karya orang lain.
Terima kasih kepada :
- Deden Sumirat Hidayat (LIPI) untuk literatur ttg PoP
- Pengembang Aplikasi Duraspace (Dspace dan Vivo).
Apakah program Sekolah Alkitab Liburan ada di gereja Anda? Perlukah diprogramkan? Jika sudah ada, apa-apa saja yang perlu dipertimbangkan lagi? Pak Igrea Siswanto dari organisasi Life Kids Indonesia membagikannya untuk kita semua.
Informasi lebih lanjut: 0821-3313-3315 (MLC)
#SABDAYLSA #SABDAEvent #ylsa #yayasanlembagasabda #SABDAAlkitab #Alkitab #SABDAMLC #ministrylearningcenter #digital #sekolahAlkitabliburan #gereja #SAL
2. Data Diri
Dwi Fajar Saputra (Dudu) : 085693341215
• FK UPN Veteran Jakarta
• FPPTI DKI Jakarta
• Komunitas SLiMS Banten
• Relawan Jurnal Indonesia Korda DKI Jakarta
Portfolio (2 Tahun Terakhir) :
1. Sistem repositori institusi UMMI : eprints
2. Sistem repositori institusi UNSADA : eprints
3. Trisakti University Collection of scholarly
and academic papers : eprints
4. Sistem repositori institusi UTU : eprints
5. Sistem repositori institusi Kementerian
Pendidikan dan Kebudayaan RI : eprints
6. Penulis buku = Eprints : Aplikasi Pengelolaan
Repositori Institusi
3. Daftar Isi
• Pendahuluan
• Tujuan
• Dasar Hukum
• Sekilas Aplikasi Eprints
• Kegunaan
• Perbandingan
• Persiapan Implementasi
• Kesimpulan
4. Pendahuluan
1. Adanya kebutuhan akan suatu sistem yang
handal untuk mendukung pengelolaan
repositori institusi.
2. Adanya keinginan untuk mempercepat
target tertentu seperti webometrics dan
indeksasi.
5. Sistem Handal
1. Banyaknya materi digital yang harus
dikelola oleh sebuah instansi.
2. Sistem yang ada, tidak mendukung penuh
pengelolaan format materi digital seperti
image, dll.
3. Biaya pemutakhiran sistem yang tergolong
mahal.
6. Target Tertentu
1. Keinginan agar sistem repositori institusi
berperan untuk meningkatkan
webometrics lembaga.
2. Kebutuhan agar materi digital dapat
terindeks secara cepat/lengkap di mesin
indeks.
7. Tujuan
1. Memberikan informasi terkait pentingnya
sistem repositori institusi untuk
diimplementasikan di perpustakaan
khusus.
2. Memberikan informasi tentang aplikasi
eprints yang dapat digunakan untuk
sistem repositori institusi.
8. Dasar Hukum
1. Undang Undang Republik Indonesia
Nomor 43 Tahun 2007.
2. Standar Nasional Perpustakaan 006:2011
Tentang Perpustakaan Khusus Instansi
Pemerintah.
9. Undang Undang Republik Indonesia
Nomor 43 Tahun 2007
Pasal 27 :
Perpustakaan Khusus diselenggarakan sesuai
dengan standar nasional perpustakaan.
11. Titik Kritis dari Dasar Hukum
Berkaitan dengan sistem :
Sistem mampu
mengelola
berbagai format
media.
Sistem dapat
berperan sebagai
media
pelestarian
koleksi.
Sistem dapat
dimanfaatkan
oleh publik.
Sistem mampu
depositkan
berbagai format
media.
12. Berkaitan dengan Repositori Institusi
di Perpustakaan Khusus
1. Koleksi menghasilkan bermacam format
materi digital seperti peraturan
(pdf/image), iklan layanan masyarakat
(video), hasil karya ilmiah pegawai (pdf),
sosialisasi (ppt), dll. -> Memerlukan
aplikasi yang handal karena berkaitan
dengan pengelolaan, penyimpanan
(deposit) dan preservasi.
2. Dapat diakses oleh publik. -> Web Based.
13. Sekilas Aplikasi Eprints
• Perangkat lunak berbasis web
• Lisensi GNU Public Licence Version 3
• Core program language : perl
• DBMS : mysql
• OS : Ubuntu 14.04 / Debian 7
14. Kegunaan (Umum)
1. Menjalankan SNP 006:2011 Tentang
Perpustakaan Khusus terutama fungsi
deposit.
2. Mendukung pengelolaan koleksi dengan
baik.
3. Meminimalisir kebutuhan tempat dan
tenaga.
4. Efektif dalam hal penyebarluasan.
15. Kegunaan (Aplikasi)
1. Mampu mengelola bermacam format materi
digital (metadata-simpan-menampilkan).
2. Memiliki dashboard administrator yang
menyediakan text editor bagi pustakawan
(tanpa harus ke root server).
3. Ramah terhadap seo dan mesin indeks (google
& scholar google).
4. Memiliki proses bisnis yang berkesinambungan
untuk meminimalisir salah entri (user-reviewer-
administrator).
16. Perbandingan
SLiMS & Eprints
1. SLiMS dibuat untuk sistem manajemen
perpustakaan, sedangkan Eprints dibuat untuk
sistem repositori institusi.
Sistem manajemen perpustakaan tersedia fitur
keanggotaan, sirkulasi, stock take. Fitur-fitur
tersebut dapat digunakan untuk mendukung
berjalannya roda perpustakaan berbasis teknologi
informasi. Sedangkan Eprints tidak menyediakan
fitur – fitur yang disebutkan diatas. Namun fokus
pada pengelolaan materi digital.
17. 2. SLiMS proses bisnisnya dimulai dari membuat
peraturan peminjaman/keanggotaan-isi daftar
anggota-isi bibliografi-sirkulasi-stock take.
Sedangkan Eprints dimulai dari Type-Upload-Details-
Subjects-Deposit.
Dalam SLiMS bila keanggotaan tidak diisi terlebih
dahulu, maka sirkulasi tidak akan bisa dijalankan
sehingga user harus memiliki pengetahuan yang
jelas mengenai operasionalkan SLiMS. Sedangkan
Eprints lebih user friendly karena ada petunjuk
arahnya dalam menjalankan proses bisnisnya.
18. 3. SLiMS menggunakan AACR II/RDA (Akasia) dalam
metadata deskripsi. Sedangkan Eprints
menggunakan beragam metadata deskripsi
disesuaikan dengan format materi digital yang akan
dientri.
Pada SLiMS bila entri data koleksi harus mengisi
format metadata deskripsi berdasarkan AACR II
(dibawah Akasia)/ RDA (start Akasia) sehingga bisa
menghasilkan keluaran salah satunya kartu katalog.
Bila Eprints setiap materi digital yang akan dientri
memiliki format metadata deskripsi yang berbeda-
beda sehingga menyesuaikan dengan “ke-khasan ”
dari materi digital tersebut.
19. 4. SLiMS belum dapat mendukung secara penuh
format materi digital sedangkan Eprints hampir
semua format materi digital dapat didukung baik
dari segi metadata, penyimpanan dan penampilan.
Di SLiMS jika mencari koleksi format JPG/PNG ketika
ditelusur pada pencarian akan muncul pada bagian
lampiran namun tidak dapat dilihat (review) terlebih
dahulu, bila di-klik akan melakukan pengunduhan
file. Berbeda dengan Eprints yang secara default
bisa muncul proses review dan melihat file secara
penuh.
20. 5. Eprints lebih ramah search engine seperti google,
ketimbang SLiMS karena menerapkan struktur data
backlink (banyak menempatkan file yang sama
didalam folder yang berbeda).
Karena SLiMS hanya menempatkan file pada 1
folder penyimpanan saja, berbeda dari Eprints yang
menyimpan di lebih dari 3 folder penyimpanan.
21. 6. Eprints lebih menerapkan konsep Search Enginge
Optimization (SEO) ketimbang SLiMS salah satunya
sub direktori root domain :
http://repository.utu.ac.id/7/ -> Eprints
https://perpustakaan.setneg.go.id/index.php?p=show
_detail&id=15042 -> SLiMS
22. Persiapan Implementasi
1. Menyiapkan sumber daya manusia.
2. Menyiapkan materi digital.
3. Membuat kebijakan tertulis.
4. Mempersiapkan infrastruktur
teknologi.
5. Peningkatan kompetensi bagi SDM
(Tahap lanjut). (Saputra : 2017)
23. Kesimpulan
1. Perpustakaan khusus berfungsi sebagai pusat
deposit oleh karena itu penting untuk
menerapkan sistem repositori institusi pada
era saat ini agar menghasilkan layanan yang
efektif dan efisien.
2. Aplikasi eprints dapat dijadikan salah satu
alternatif alat bantu untuk mendukung
pelaksanaan sistem repositori institusi karena
tergolong sudah teruji dan mendukung
bermacam format materi digital.