投稿時間:2022-06-28 17:36:17 RSSフィード2022-06-28 17:00 分まとめ(47件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	＠IT Security&Trustフォーラム 最新記事一覧	企業の60％がゼロトラスト採用へ、しかしメリット享受は？　Gartnerがセキュリティ将来予測	https://atmarkit.itmedia.co.jp/ait/articles/2206/28/news133.html	gartner	2022-06-28 16:15:00
ROBOT	ロボスタ	日本科学未来館 自由な発想から生まれたロボット技術を体験できる「空想⇔実装 ロボットと描く私たちの未来」7月8日から開催	https://robotstart.info/2022/06/28/fantasy-implementation-robot.html	日本科学未来館自由な発想から生まれたロボット技術を体験できる「空想⇔実装ロボットと描く私たちの未来」月日から開催シェアツイートはてブ日本科学未来館は研究開発の「いま」を見せる新シリーズ企画「MiraicanNOW」ミライキャンナウを開始することを発表した。	2022-06-28 07:40:09
IT	＠IT 全フォーラム 最新記事一覧	企業の60％がゼロトラスト採用へ、しかしメリット享受は？　Gartnerがセキュリティ将来予測	https://atmarkit.itmedia.co.jp/ait/articles/2206/28/news133.html	gartner	2022-06-28 16:15:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] デル、円形デザインを採用した多機能USBハブ	https://www.itmedia.co.jp/pcuser/articles/2206/28/news177.html	itmediapcuser	2022-06-28 16:48:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] コンビニバイト経験を「ガクチカ」に　ファミマが就活生に“自己PRの書き方”を教える理由	https://www.itmedia.co.jp/business/articles/2206/28/news154.html	ITmediaビジネスオンラインコンビニバイト経験を「ガクチカ」にファミマが就活生に“自己PRの書き方を教える理由ファミリーマートは、店舗で働く大学生を対象に、就活支援オンライン講座を開催する。	2022-06-28 16:45:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 「上場直前まで苦しんだ」ランサーズ小沼CFOが浴びたIPOの洗礼	https://www.itmedia.co.jp/business/articles/2206/28/news077.html	itmedia	2022-06-28 16:30:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] Windows 8.1のサポートは2023年1月に終了　拡張セキュリティ更新プログラムは提供されず	https://www.itmedia.co.jp/pcuser/articles/2206/28/news173.html	itmediapcuserwindows	2022-06-28 16:30:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ランサーズ小沼CFOが「一からやり直し」、“事業部の責任者”も兼任する訳	https://www.itmedia.co.jp/business/articles/2206/28/news097.html	itmedia	2022-06-28 16:30:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ミニストップ、ソフトクリームのスプーンを“食べるスプーン”に変更	https://www.itmedia.co.jp/business/articles/2206/28/news171.html	itmedia	2022-06-28 16:20:00
AWS	AWS Japan Blog	【Amazon Game Tech Night 開催報告】5/17 ゲームワークロードで AWS Graviton の活用	https://aws.amazon.com/jp/blogs/news/%E3%80%90amazon-game-tech-night-%E9%96%8B%E5%82%AC%E5%A0%B1%E5%91%8A%E3%80%915-17-%E3%82%B2%E3%83%BC%E3%83%A0%E3%83%AF%E3%83%BC%E3%82%AF%E3%83%AD%E3%83%BC%E3%83%89%E3%81%A7-aws-graviton-%E3%81%AE/	amazongametechnight	2022-06-28 07:44:27
python	Pythonタグが付けられた新着投稿 - Qiita	Jupyter NotebookをMacにインストールした方法	https://qiita.com/t_dragon/items/907ca8b32550d6155c3a	jupyterno	2022-06-28 16:32:27
js	JavaScriptタグが付けられた新着投稿 - Qiita	Unique Array By Key 【JavaScript】	https://qiita.com/DeepRecommend/items/43fe4df6ac591d67bd92	values	2022-06-28 16:43:35
js	JavaScriptタグが付けられた新着投稿 - Qiita	【Vue】dataプロパティのオブジェクト追加？ちょっと待った～	https://qiita.com/kine25/items/7176ba6c9b9de0ba88e1	thisdata	2022-06-28 16:05:49
Docker	dockerタグが付けられた新着投稿 - Qiita	2分で分かるDocker～コンテナ入門～	https://qiita.com/Toru_Kubota/items/64d1d584c40f9a62a105	docker	2022-06-28 16:48:33
Git	Gitタグが付けられた新着投稿 - Qiita	Github(初期設定からリモートリポジトリにプッシュ)	https://qiita.com/tumu1632/items/9ab206aedcdf70e4097f	gitconfigglob	2022-06-28 16:57:56
Git	Gitタグが付けられた新着投稿 - Qiita	あるコミットで何をしたかを見る	https://qiita.com/masatom86650860/items/ed4f8606fcac050f76ec	mbptraininggitshowcommit	2022-06-28 16:57:04
Git	Gitタグが付けられた新着投稿 - Qiita	Gitトークンを作成してみた	https://qiita.com/Fledgling_engineer/items/ba7ee84e7d416e27140a	ltgtde	2022-06-28 16:46:02
海外TECH	DEV Community	Run Laravel 9 on Docker in 2022 [Tutorial Part 4]	https://dev.to/pascallandau/run-laravel-9-on-docker-in-2022-tutorial-part-4-1gmf	Run Laravel on Docker in Tutorial Part This article appeared first on at Run Laravel on Docker in Tutorial Part In this third subpart of the fourth part of this tutorial series on developing PHP on Docker we will install Laravel and make sure our setup works for Artisan Commands a Redis Queue and Controllersfor the front end requests All code samples are publicly available in my Docker PHP Tutorial repository on Github You find the branch for this tutorial at part run laravel docker in All published parts of the Docker PHP Tutorial are collected under a dedicated page at Docker PHP Tutorial The previous part was PhpStorm Docker and Xdebug on PHP in and the following one is Set up PHP QA tools and control them via make If you want to follow along please subscribe to the RSS feed or via email to get automatic notifications when the next part comes out Table of contentsIntroductionInstall extensionsInstall LaravelUpdate the PHP POCconfigdatabase connectionqueue connectionControllersCommandsJobs and workersTestsMakefile updatesClearing the queueRunning the POCWrapping up IntroductionThe goal of this tutorial is to run the PHP POC from part using Laravel as a framework instead of plain PHP We ll use the newest version of Laravel Laravel that was released at the beginning of February Install extensionsBefore Laravel can be installed we need to add the necessary extensions of the framework and all its dependencies to the php base image File docker images php base Dockerfile RUN apk add update no cache php curl TARGET PHP VERSION Install LaravelWe ll start by creating a new Laravel project with composercomposer create project prefer dist laravel laravel tmp laravel no install no scriptsThe files are added to tmp laravel because composer projects cannot be created in non empty folders so we need to create the project in a temporary location first and move it afterwards Since I don t have PHP installed on my laptop I ll execute the command in the application docker container viamake execute in container DOCKER SERVICE NAME application COMMAND composer create project prefer dist laravel laravel tmp laravel no install no scripts and then move the files into the application directory viarm rf public tests composer phpunit xmlmake execute in container DOCKER SERVICE NAME application COMMAND bash c mv n tmp laravel amp amp rm f tmp laravel cp env example envNotescomposer install is skipped via no install to avoid having to copy over the vendor folder which is super slow on Docker Desktop existing directories cannot be overwritten by mv thus I remove public and tests upfront as well as the composer and phpunit config files mv uses the n flag so that existing files like our editorconfig are not overwrittenI need to use bash c to run the command in the container because otherwise the wildcard would have no effect in the container To finalize the installation I need to install the composer dependencies and execute the create project scripts defined in composer json make composer ARGS installmake composer ARGS run script post create project cmd Since our nginx configuration was already pointing to the public directory we can immediately open in the browser and should see the frontpage of a fresh Laravel installation Update the PHP POC configWe need to update the connection information for the database and the queue previously configured via dependencies php in the env file database connectionDB CONNECTION mysqlDB HOST mysqlDB PORT DB DATABASE application dbDB USERNAME rootDB PASSWORD secret mysql root password queue connectionQUEUE CONNECTION redisREDIS HOST redisREDIS PASSWORD secret redis password ControllersThe functionality of the previous public index php file now lives in the HomeController at app Http Controllers HomeController phpclass HomeController extends Controller use DispatchesJobs public function invoke Request request QueueManager queueManager DatabaseManager databaseManager View jobId request gt input dispatch null if jobId null job new InsertInDbJob jobId this gt dispatch job return this gt getView Adding item jobId to queue if request gt has queue var RedisQueue redisQueue redisQueue queueManager gt connection redis redisQueue gt getRedis gt connection queueItems redis gt lRange queues default content Items in queue n var export queueItems true return this gt getView content if request gt has db items databaseManager gt select databaseManager gt raw SELECT FROM jobs content Items in db n var export items true return this gt getView content content lt lt lt HTML lt ul gt lt li gt lt a href dispatch foo gt Dispatch job foo to the queue lt a gt lt li gt lt li gt lt a href queue gt Show the queue lt a gt lt li gt lt li gt lt a href db gt Show the DB lt a gt lt li gt lt ul gt HTML return this gt getView content private function getView string content View return view home gt with content gt content Its content is displayed via the home view located at resources views home blade php lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt content lt body gt lt html gt The controller is added as a route in routes web php Route get App Http Controllers HomeController class gt name home CommandsWe will replace the setup php script with a SetupDbCommand that is located at app Commands SetupDbCommand phpclass SetupDbCommand extends Command var string protected name app setup db var string protected description Run the application database setup protected function getOptions array return drop null InputOption VALUE NONE If given the existing database tables are dropped and recreated public function handle drop this gt option drop if drop this gt info Dropping all database tables this gt call WipeCommand class this gt info Done this gt info Running database migrations this gt call MigrateCommand class this gt info Done Register it the AppServiceProvider in app Providers AppServiceProvider php public function register this gt commands App Commands SetupDbCommand class and update the setup db target in make application setup mk to run the artisan Command PHONY setup dbsetup db Setup the DB tables EXECUTE IN APPLICATION CONTAINER php artisan app setup db ARGS We will also create a migration for the jobs table in database migrations create jobs table php return new class extends Migration public function up void Schema create jobs function Blueprint table table gt id table gt string value Jobs and workersWe will replace the worker php script with InsertInDbJob located at app Jobs InsertInDbJob phpclass InsertInDbJob implements ShouldQueue use Dispatchable InteractsWithQueue Queueable public function construct public readonly string jobId public function handle DatabaseManager databaseManager databaseManager gt insert INSERT INTO jobs value VALUES this gt jobId though this will only handle the insertion part For the worker itself we will use the native Illuminate Queue Console WorkCommand viaphp artisan queue workWe need to adjust the docker images php worker Dockerfile and changeARG PHP WORKER COMMAND php APP CODE PATH worker php toARG PHP WORKER COMMAND php APP CODE PATH artisan queue work Since this change takes place directly in the Dockerfile we must now rebuild the image make docker build image DOCKER SERVICE NAME php workerand restart it make docker up TestsI d also like to take this opportunity to add a Feature test for the HomeController at tests Feature App Http Controllers HomeControllerTest php class HomeControllerTest extends TestCase public function setUp void parent setUp this gt setupDatabase this gt setupQueue dataProvider invoke dataProvider public function test invoke array params string expected void urlGenerator this gt getDependency UrlGenerator class url urlGenerator gt route home params response this gt get url response gt assertStatus gt assertSee expected false public function invoke dataProvider array return default gt params gt expected gt lt lt lt TEXT lt li gt lt a href dispatch foo gt Dispatch job foo to the queue lt a gt lt li gt lt li gt lt a href queue gt Show the queue lt a gt lt li gt lt li gt lt a href db gt Show the DB lt a gt lt li gt TEXT database is empty gt params gt db expected gt lt lt lt TEXT Items in db array TEXT queue is empty gt params gt queue expected gt lt lt lt TEXT Items in queue array TEXT public function test shows existing items in database void databaseManager this gt getDependency DatabaseManager class databaseManager gt insert INSERT INTO jobs id value VALUES foo urlGenerator this gt getDependency UrlGenerator class params db url urlGenerator gt route home params response this gt get url expected lt lt lt TEXT Items in db array gt object array id gt value gt foo TEXT response gt assertStatus gt assertSee expected false public function test shows existing items in queue void queueManager this gt getDependency QueueManager class job new InsertInDbJob foo queueManager gt push job urlGenerator this gt getDependency UrlGenerator class params queue url urlGenerator gt route home params response this gt get url expectedJobsCount lt lt lt TEXT Items in queue array gt TEXT expected lt lt lt TEXT jobId s foo TEXT response gt assertStatus gt assertSee expectedJobsCount false gt assertSee expected false The test checks the database as well as the queue and uses the helper methods this gt setupDatabase and this gt setupQueue that I defined in the base test case at tests TestCase php as follows template T param class string lt T gt className return T protected function getDependency string className return this gt app gt get className protected function setupDatabase void databaseManager this gt getDependency DatabaseManager class actualConnection databaseManager gt getDefaultConnection testingConnection testing if actualConnection testingConnection throw new RuntimeException Database tests are only allowed to run on default connection testingConnection The current default connection is actualConnection this gt ensureDatabaseExists databaseManager this gt artisan SetupDbCommand class drop gt true protected function setupQueue void queueManager this gt getDependency QueueManager class actualDriver queueManager gt getDefaultDriver testingDriver testing if actualDriver testingDriver throw new RuntimeException Queue tests are only allowed to run on default driver testingDriver The current default driver is actualDriver this gt artisan ClearCommand class protected function ensureDatabaseExists DatabaseManager databaseManager void connection databaseManager gt connection try connection gt getPdo catch PDOException e e g SQLSTATE HY Unknown database testing if e gt getCode throw e config connection gt getConfig config database connector new MySqlConnector pdo connector gt connect config database connection gt getDatabaseName pdo gt exec CREATE DATABASE IF NOT EXISTS database The methods ensure that the tests are only executed if the proper database connection and queue driver is configured This is done through environment variables and I like using a dedicated env file located at env testing for all testing ENV values instead of defining them in the phpunit xml config file via lt env gt elements File env testingDB CONNECTION testingDB DATABASE testingQUEUE CONNECTION testingREDIS DB The corresponding connections have to be configured in the config files File config database phpreturn connections gt testing gt driver gt mysql url gt env DATABASE URL host gt env DB HOST port gt env DB PORT database gt env DB DATABASE testing username gt env DB USERNAME password gt env DB PASSWORD unix socket gt env DB SOCKET charset gt utfmb collation gt utfmb unicode ci prefix gt prefix indexes gt true strict gt true engine gt null options gt extension loaded pdo mysql array filter PDO MYSQL ATTR SSL CA gt env MYSQL ATTR SSL CA redis gt testing gt url gt env REDIS URL host gt env REDIS HOST password gt env REDIS PASSWORD port gt env REDIS PORT database gt env REDIS DB File config queue phpreturn connections gt testing gt driver gt redis connection gt testing gt refers to the database redis testing config entry queue gt env REDIS QUEUE default retry after gt block for gt null after commit gt false The tests can be executed via make test make testENV local TAG latest DOCKER REGISTRY docker io DOCKER NAMESPACE dofroscra APP USER NAME application APP GROUP NAME application docker compose p dofroscra local env file docker env f docker docker compose docker compose yml f docker docker compose docker compose local yml exec T user application php worker vendor bin phpunit c phpunit xmlPHPUnit by Sebastian Bergmann and contributors Time Memory MBOK tests assertions Makefile updates Clearing the queueFor convenience while testing I added a make target to clear all items from the queue in make application commands mk PHONY clear queueclear queue Clear the job queue EXECUTE IN APPLICATION CONTAINER php artisan queue clear ARGS Running the POCSince the POC only uses make targets and we basically just refactored them there is no modification necessary to make the existing test sh work bash test sh Building the docker setup Starting the docker setup Clearing DBENV local TAG latest DOCKER REGISTRY docker io DOCKER NAMESPACE dofroscra APP USER NAME application APP GROUP NAME application docker compose p dofroscra local env file docker env f docker docker compose docker compose yml f docker docker compose docker compose local yml exec T user application application php artisan app setup db drop Dropping all database tables Dropped all tables successfully Done Running database migrations Migration table created successfully Migrating create users tableMigrated create users table ms Migrating create password resets tableMigrated create password resets table ms Migrating create failed jobs tableMigrated create failed jobs table ms Migrating create personal access tokens tableMigrated create personal access tokens table ms Migrating create jobs tableMigrated create jobs table ms Done Stopping workersENV local TAG latest DOCKER REGISTRY docker io DOCKER NAMESPACE dofroscra APP USER NAME application APP GROUP NAME application docker compose p dofroscra local env file docker env f docker docker compose docker compose yml f docker docker compose docker compose local yml exec T user application php worker supervisorctl stop worker worker worker stoppedworker worker stoppedworker worker stoppedworker worker stopped Ensuring that queue and db are empty lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Items in queuearray lt body gt lt html gt lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Items in dbarray lt body gt lt html gt Dispatching a job foo lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Adding item foo to queue lt body gt lt html gt Asserting the job foo is on the queue lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Items in queuearray gt uuid ea a abf adbd displayName App Jobs InsertInDbJob job Illuminate Queue CallQueuedHandler call maxTries null maxExceptions null failOnTimeout false backoff null timeout null retryUntil null data commandName App Jobs InsertInDbJob command O App Jobs InsertInDbJob s jobId s foo s job N s connection N s queue N s chainConnection N s chainQueue N s chainCatchCallbacks N s delay N s afterCommit N s middleware a s chained a id IkPNyGZcZXWCCgtqtSdqUZFU attempts lt body gt lt html gt Starting the workersENV local TAG latest DOCKER REGISTRY docker io DOCKER NAMESPACE dofroscra APP USER NAME application APP GROUP NAME application docker compose p dofroscra local env file docker env f docker docker compose docker compose yml f docker docker compose docker compose local yml exec T user application php worker supervisorctl start worker worker worker startedworker worker startedworker worker startedworker worker started Asserting the queue is now empty lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Items in queuearray lt body gt lt html gt Asserting the db now contains the job foo lt DOCTYPE html gt lt html gt lt head gt lt meta charset utf gt lt head gt lt body gt Items in dbarray gt object array id gt value gt foo lt body gt lt html gt Wrapping upCongratulations you made it If some things are not completely clear by now don t hesitate to leave a comment Laravel should now be up and running on the previously set up docker infrastructure In the next part of this tutorial we will Set up PHP QA tools and control them via make Please subscribe to the RSS feed or via email to get automatic notifications when this next part comes out	2022-06-28 07:35:36
海外TECH	DEV Community	Oh no! An error occurred, what is to be done next?	https://dev.to/hr21don/oh-no-an-error-occurred-what-is-to-be-done-next-54g2	Oh no An error occurred what is to be done next Now every software developer encounters an issue or bug in their code that doesn t always function as we expect it to try and do Unfortunately the immediate reaction of most beginners is to travel into denial In this post we re going to clarify what debugging is why we do it and how can we get better at it We ll also reassess why debugging won t reveal all the issues or bugs in our code What is debugging Debugging is the process of running your code step by step with a debugging tool like Visual Studio to seek out the exact point where you made a programming mistake Usually you ll understand what corrections you need to make in your code and debugging tools often allow you to make temporary changes so you can continue running the program Why do we debug There s no magic solution for bugs Usually it takes a mixture of googling logging our code and checking our logic against what is really happening Debugging certainly helps break complex problems into simple ones where the use of a debugger helps to point out what the bug or fault is where it has occurred and the way it is caused A debugger helps to investigate your code when it gets to the place where you suspect a problem of logic or implementation You may do the identical thing by adding print messages to your code but it s a lot less convenient and versatile compared to console log How we can get better at it Below I ll outline some ways I ve found useful for debugging projects TestingAnother way of debugging your code is by adding code tests These come in many varieties and include unit tests integration tests functional tests and more These types of tests are created to save lots of time and check whether the development environment is running correctly When the tests do not pass it always indicates a bug that needs to be fixed The code that failed is not allowed to move on to the following phase until the bugs are fixed and the tests pass Pay attention to error messages In almost every development environment if your code fails you ll likely encounter an error message that explains why your code is failing Good error messages are helpful and supply you with a file and line number that represents the source of the problem whereas bad error messages are undecipherable and don t add up to anyone but the one who programmed it in the first place We ve all seen them usually in very frustrating moments when our production environment is not working properly Googling As beginners the possibility that our problem has never been encountered before is pretty low It s worth leaning on the wisdom of others who came before If the error message you get isn t clear to you or you can t figure out why you re getting it an honest initiative would be to Google it One of the many amazing things about software engineering is that the web community is huge Almost surely there are heaps of people already that have faced the same bug you re facing which has been solved and explained so other people don t have to struggle with it too Official documentation should be the first thing to check either when you re learning something new or dealing with an error Official docs are typically the most complete and updated source of knowledge for any given tool It sometimes may feel tedious or overwhelming to go through most technical information but in the long run I think it saves time Debugging Tools Debugging tools are usually built into the integrated development environments IDEs developers use to write code There are also debuggers that are included with a number of online web browsers including Chrome Firefox and Opera for debugging web applications Debuggers are utility tools that are designed to allow programmers to create breakpoints in code Once they run code with a breakpoint in it the code will stop running at the breakpoint which allows the developer to go through the code line by line and examine the variables at each step to determine what went wrong Using a debugger is the most advanced method you could use and is not needed when other techniques will work Check Your Logic If we ve made it this far then it s a good solution to go through your code line by line reading it and explaining it out loud as you go which in software engineering is known as the rubber duck technique The idea is to force yourself to truly read your code rather than just assuming you know what it does In this way you can check the logic in your mind versus what is actually happening in your code Error handling Another method of debugging your code is using error handling Code that does not use error handling will often crash when it encounters a bug You can use error handling to catch an error and log the error data within a database before it has a chance to crash the application Error handling is perfect for finding bugs in a production environment because errors are often collected as they occur and then analyzed later to determine what type of bug is causing them ーall without causing a bad experience for the software user Commenting things out Often times you ll end up turning functional code into comments that won t be executed You begin by commenting out code in the part of the production environment where you think the problem is until the error stops happening Then you just add each line of code back one at a time until the bug shows up again and once it does you ve pinpointed where the bug is occurring Asking for help While this is often the last method on the list it s one of the most important and is commonly overlooked Most times you will be working with other developers on the same project who may know more about some of the code than you do Even if they don t they may have worked on the part of the application that has the bug But you won t know unless you ask Another reason to ask other developers for help is that after you look at the same code for a while you may be too close to the problem and choose the wrong route to a solution Even if the developers you ask don t work on your project they can often help you find the bug by giving you a fresh perspective ConclusionIf you ve tried to no avail or you don t have any colleagues on hand then it might be time to make your first stack overflow post Useful ResourcesWhat are browser developer tools MDN DocsHow to debug for absolute beginners Microsoft Docs First look at the Visual Studio Debugger Microsoft Docs	2022-06-28 07:17:09
海外TECH	CodeProject Latest Articles	VoiceNET Library	https://www.codeproject.com/Articles/5336014/VoiceNET-Library	command	2022-06-28 07:13:00
医療系	医療介護 CBnews	直通階段1つの建築物「重点的に立入検査を」-消防庁が大阪市北区ビル火災の検討会報告書を公表	https://www.cbnews.jp/news/entry/20220628164021	大阪市北区	2022-06-28 17:00:00
医療系	医療介護 CBnews	依存症対策総合支援事業で専門医療機関選定を推進-厚労省が「五か年戦略」のフォローアップ公表	https://www.cbnews.jp/news/entry/20220628161823	依存症専門医療機関	2022-06-28 16:30:00
金融	生命保険協会	株式会社かんぽ生命保険の新規業務の届出について	https://www.seiho.or.jp/info/news/2022/20220628.html	株式会社	2022-06-28 16:09:20
ニュース	BBC News - Home	Texas migrant deaths: At least 46 found dead in abandoned lorry	https://www.bbc.co.uk/news/world-us-canada-61961871?at_medium=RSS&at_campaign=KARANGA	border	2022-06-28 07:08:24
ニュース	BBC News - Home	Zara Aleena: Woman killed in Ilford was kind soul, say friends	https://www.bbc.co.uk/news/uk-england-london-61963365?at_medium=RSS&at_campaign=KARANGA	whole	2022-06-28 07:39:35
ニュース	BBC News - Home	Defence Secretary Ben Wallace seeks more military spending over Russian threat	https://www.bbc.co.uk/news/uk-61961675?at_medium=RSS&at_campaign=KARANGA	russia	2022-06-28 07:08:20
ニュース	BBC News - Home	Heathrow told to reduce passenger charge	https://www.bbc.co.uk/news/business-61933731?at_medium=RSS&at_campaign=KARANGA	aviation	2022-06-28 07:26:41
ニュース	BBC News - Home	Will Sweden and Finland go from neutral to Nato?	https://www.bbc.co.uk/news/world-europe-61397478?at_medium=RSS&at_campaign=KARANGA	finland	2022-06-28 07:08:07
ニュース	BBC News - Home	Tour de France: Geraint Thomas among four Britons in Ineos squad along with Tom Pidcock, Adam Yates and Luke Rowe	https://www.bbc.co.uk/sport/cycling/61952346?at_medium=RSS&at_campaign=KARANGA	Tour de France Geraint Thomas among four Britons in Ineos squad along with Tom Pidcock Adam Yates and Luke RoweGeraint Thomas is named in the Ineos Grenadiers team for the Tour de France along with three other British riders	2022-06-28 07:43:52
ビジネス	不景気.com	長崎の茶小売「お茶の山口園」に破産決定、負債29億円 - 不景気com	https://www.fukeiki.com/2022/06/ochano-yamaguchien.html	信用調査会社	2022-06-28 07:42:55
サブカルネタ	ラーブロ	博多とんこつ 天神旗＠上新庄（大阪府）　「老塩とんこつ（こってり）」	http://ra-blog.net/modules/rssc/single_feed.php?fid=200492	大阪市東淀川区	2022-06-28 08:31:46
北海道	北海道新聞	最低賃金１５００円へ引き上げを　全労連、厚労省前で訴え	https://www.hokkaido-np.co.jp/article/699029/	引き上げ	2022-06-28 16:38:54
北海道	北海道新聞	後志管内５感染　新型コロナ	https://www.hokkaido-np.co.jp/article/699057/	新型コロナウイルス	2022-06-28 16:53:00
北海道	北海道新聞	バックアラームの搭載義務化へ　トラックやバス、国交省	https://www.hokkaido-np.co.jp/article/699056/	国土交通省	2022-06-28 16:50:00
北海道	北海道新聞	大阪の教諭過労、府に賠償命令　適応障害との因果関係を認定	https://www.hokkaido-np.co.jp/article/699055/	長時間労働	2022-06-28 16:49:00
北海道	北海道新聞	猛暑日９０地点超、今年最多　山梨・甲州３８・７度	https://www.hokkaido-np.co.jp/article/699051/	日本列島	2022-06-28 16:44:00
北海道	北海道新聞	北海道と東北両電力管内の注意報は発令せず　経済産業省	https://www.hokkaido-np.co.jp/article/699044/	経済産業省	2022-06-28 16:41:08
北海道	北海道新聞	豊かな湿原知って　雨竜沼グッズ続々登場　モンベルオリジナルＴシャツも	https://www.hokkaido-np.co.jp/article/698626/	雨竜沼湿原	2022-06-28 16:36:11
北海道	北海道新聞	北欧２国とトルコ会談へ　ＮＡＴＯ首脳会議が開幕	https://www.hokkaido-np.co.jp/article/699045/	北大西洋条約機構	2022-06-28 16:33:00
北海道	北海道新聞	夏の高校野球支部予選・６月２８日の試合結果	https://www.hokkaido-np.co.jp/article/698908/	夏の高校野球	2022-06-28 16:16:07
北海道	北海道新聞	韓国の尹氏、多国間外交デビュー　初のＮＡＴＯ首脳会議出席	https://www.hokkaido-np.co.jp/article/699039/	首脳会議	2022-06-28 16:16:00
北海道	北海道新聞	プリマハム５～３０％値上げ　９月から約４００品	https://www.hokkaido-np.co.jp/article/699037/	加工品	2022-06-28 16:10:00
北海道	北海道新聞	沖縄で１７４４人感染　新型コロナ、３人死亡	https://www.hokkaido-np.co.jp/article/699034/	新型コロナウイルス	2022-06-28 16:04:00
IT	週刊アスキー	グッドスマイルカンパニー主催のイベントが開催決定！　「スマイルフェス2022」8月6日・7日開催	https://weekly.ascii.jp/elem/000/004/096/4096015/	youtube	2022-06-28 16:40:00
IT	週刊アスキー	今度はPSで夏休み！『クレヨンしんちゃん「オラと博士の夏休み」～おわらない七日間の旅～』のPS4版が今夏に世界同時発売決定	https://weekly.ascii.jp/elem/000/004/096/4096021/	nintendo	2022-06-28 16:35:00
マーケティング	AdverTimes	5月度の外食、明暗さらに　戻らない夜間需要	https://www.advertimes.com/20220628/article388447/	需要	2022-06-28 07:10:44
マーケティング	AdverTimes	世界一クリエイティブなマーケティング企業を探せ―嶋野裕介のカンヌレポート2022	https://www.advertimes.com/20220628/article388401/	電通	2022-06-28 07:02:47